Sextant, by GTM Cloud · Clean · Early access
Compare fields in Salesforce, then sync the value you trust
Sextant puts your record beside a second source, such as a data provider’s record, and marks every field as matching, different or missing. Sync the value you trust, undo it if you were wrong, and scan a whole object for records that disagree.
You know this one
Two browser windows, side by side. On the left, the Account. On the right, the record your data provider’s package keeps for the same company.
You read the address aloud, because that’s how you catch things. “Suite 200.” “Ste 200.” Same? Same. Then phone, industry, employee count. Five fields in, you’ve lost your place.
So you retype the values you trust, one at a time, and hit Save. Nobody checks whether you copied the right ones, and if one was wrong, there’s no quick way back.
How to compare fields in Salesforce against a second source
A sextant finds your position by comparing two points. Here the two points are your record and a second source: usually a data provider’s record, or a second set of fields on the same record, like billing against shipping address.
Sextant puts them on one card and gives every field a status: match, different or missing. You can sync one field, a selection or everything in one click. If it was the wrong copy, Undo restores the old value.
See it first. Take it back. Keep the receipt.
| Preview | Undo | Prove |
|---|---|---|
| Every difference is shown, with the differing part marked, before any value is copied. | Undo restores a synced value from the record’s field history. | Scans are kept and can be reported on. |
What you get
A status on every field, with counts you can click
A summary shows how many fields differ, are missing or match. Click a count to filter the rows.
One click to sync, one to take it back
Sync one field, a selection or everything. A sync respects each user’s field-level security.
Undo, from the field history
Undo restores a synced value from the record’s field history, so a wrong copy isn’t permanent.
A new comparison without code
Pick the objects, add the field pairs, choose the colors and header values, and watch a live preview as you go. Three starters give you a head start.
A scan for the records that disagree
The Scan tab checks every record of a comparison’s object and lists the ones whose fields differ. Scans are kept, and a report type is included.
How it works
- Assign access. Give admins the Admin set, and users the User or Read Only set.
- Enable objects. On the Settings tab, add the objects you want to compare and save.
- Create a comparison set. Pick the Destination and the Source, add the field pairs, or start from a template.
- Place the component. Add Sextant to the record page in Lightning App Builder and choose the set.
Two readers, two reasons
If you’re the admin
Define a comparison in a point-and-click editor: pick the objects, pair the fields, choose the colors. There’s no code and no deployment.
If you’re the one signing off
Enrichment data sits beside your own, and nobody can see where the two disagree. Sextant makes the disagreement visible on the record and across the object.
Today, and with Sextant
| Today | With Sextant |
|---|---|
| Two records open side by side, compared by eye | One card with a status on every field |
| Values retyped by hand, with typos | Sync one, some or all fields with one click |
| No way back after a wrong copy | Undo from field history |
| Data quality problems found only when a record is opened | A scan lists every record that disagrees |
Where it’s strong, and what to know first
We’d rather you find the limits here than after you install.
Where Sextant is strong
- A status on every field: match, different or missing, with counts you can click to filter
- Sync one field, a selection or everything in one click
- Undo, so a wrong copy is never permanent
- A scan that lists every record whose fields disagree
- New comparisons are configuration an admin saves, with a live preview
Good to know before you install
- The second source must already be in Salesforce, as a related record or as fields on the same record. Sextant doesn’t fetch data from a provider.
- Undo reads the record’s field history, so it needs Field History Tracking on the fields you want to take back.
- Sextant compares the field pairs you define. It doesn’t guess which fields belong together.
Questions people ask
Where does the second source come from?
From Salesforce itself. It can be a related record, such as the one your data provider’s package maintains, or a second set of fields on the same record, such as billing against shipping address. Sextant doesn’t fetch anything from a provider; the data has to be in your org already.
Can a user overwrite a field they should not touch?
No. A sync needs edit access to the destination field, so Read Only users are refused by field-level security. Sextant also has a Read Only permission set, and a custom permission hides the component from people who shouldn’t see it on the record page.
How do we find problems without opening every record?
Use the Scan tab. It checks every record of a comparison’s object and lists the ones whose fields differ. Scans are kept, so you can return to them, and a report type is included for when someone wants the list in a report.
How long does a new comparison take?
Minutes. Copy a starter, or pick two objects, add the field pairs and save. There’s no code and no deployment, and a live preview shows the comparison as you configure it. Then add Sextant to the record page in Lightning App Builder and choose the set.
How do you compare two records in Salesforce?
With Sextant, you define a comparison set: the two objects, or two sets of fields on one record, and the field pairs. The component on the record page then shows every pair with a status of match, different or missing, and marks the differing part of each value.
Can you compare billing and shipping addresses in Salesforce?
Yes. Account billing against shipping address is one of three ready-made starter sets. Copy it, adjust the field pairs if you need to, and place the component on the Account page. The other two compare Account and Contact addresses, and Contact mailing against other address.
Works well with
- Sluice: before you compare values, merge the duplicate records so you’re comparing the right one.
- Wake: keep a log of who changed a field and what it was, beyond the native 20 fields per object.
- Portage: when the better values are in a file, import them with a preview first.
Sextant is part of the Clean stage of the lead-to-renewal map. Not sure how far your records drift from your provider’s? Book a Data Health Check. Every app installs by itself. None needs another.
Built on the platform
- Native to Salesforce. No external service.
- Respects security. A sync needs edit access to the destination field, and Read Only users are refused by field-level security.
- Three permission sets, plus a custom permission to hide the component from people without access.
- In-app guides for admins and users, in English, German, Spanish, French (Canada) and Portuguese (Brazil).
Point it at the two records you compare by eye
Ask for early access and a walk-through with a comparison built from your own objects. Watch the differences appear, sync one, and take it back.