Who can use this feature?
- All roles with access level "high"
- Available on all plans
Once the Salesforce integration is configured, you can begin mapping "synced" fields from Salesforce to your Catalyst instance. For each account, opportunity, and contact object, you will map core/system default or user created fields.
Synced fields are bi-directionally populated from Salesforce; your team can read and edit these fields in Catalyst.
Map Salesforce fields to core/system Catalyst fields
Core and system default fields are fields that already in Catalyst. Individually map the fields under each object. See below for special considerations for some fields (team member, user reference, dependent picklists).
If you decide to change which Salesforce field is mapped to a Catalyst field after data has already been synced, Salesforce will be treated as the source of truth. This means that all Catalyst field data will be overwritten by the data in the newly-mapped Salesforce field. If you would like the Catalyst data to be used instead, be sure to export the Catalyst data and upload to the new Salesforce field before re-mapping.
- In Catalyst, navigate to Settings > Object Configuration.
- Open one of your objects (e.g., accounts).
- Sort by Category, and click on one of the core fields (e.g., Customer Success Manager).
- Within the window, choose the Salesforce field that best corresponds with the Catalyst field. For example, matched the Customer Success Manager field to the CSM or owner fields you use in Salesforce for the same purpose.
Available fields are based on the permissions used for the Salesforce integration user. Newly-created fields in Salesforce will sync to Catalyst within 5 hours.
- Click Update.
- Continue mapping for each relevant system or core field.
Team member fields
Team member fields are pulled into Catalyst from Salesforce automatically (indicated with an asterisk* next to the field name). These fields are created based on the team object in Salesforce and correspond to the different team member roles that are available within your Salesforce instance.
You cannot remove or unmap team member fields in Catalyst; they are not visible within object configuration and are locked fields. Catalyst users can reference the "team member" fields as segment columns and in the fields modules on account- or opportunity-level layouts (depending on which object with which it's associated).
User reference fields
After mapping Salesforce user reference field to Catalyst, the integration generates a complete list of Salesforce users, including inactive Salesforce users. Filters on lookup reference fields are not supported. For example, let's say that you've mapped your Salesforce "Customer Success Manager" field to a Catalyst "Customer Success Manager Field", and mapped your Salesforce "Implementation Manager" field to a Catalyst "Implementation Manager Field."
When filtering by either of these fields in Catalyst, the full list of Salesforce users appears as options for each of these fields.
Map Salesforce fields to new Catalyst fields
User created "synced" fields are new fields you need to create in Catalyst that you want to map with Salesforce—that aren't already core or system default. See below for special considerations for some fields (dependent picklist).
Character limits for local Catalyst text-based fields do not apply to fields synced from Salesforce.
- In Catalyst, navigate to Settings > Object Configuration.
- Open one of your objects (e.g., accounts).
- Click +Add Field.
- Choose Synced Field, and click Next.
- In the Synced to drop-down, choose one of the Salesforce fields to map. Available fields are based on the permissions used for the Salesforce integration user.
The input type is automatically identified. - Optionally adjust the display name as it will appear in Catalyst, and add a description to the field.
- Click Create.
Newly-created fields mapped to Salesforce will sync to Catalyst within 5 hours.
Dependent picklists
Dependent picklists ensure your Catalyst team chooses from values that depend on selections from another field (i.e., the controlling field). For example, a "Reason" picklist on the opportunity object may have values depend on the opportunity "Stage" picklist (e.g., if closed won, reasons are superior features or lower price; if closed lost, reasons are inferior features or higher price).
To ensure dependent fields are represented in Catalyst, set up the dependent picklist configuration in Salesforce first. Controlling fields can be any picklist (with at least one and fewer than 300 values) or checkbox field on the same record. Then, map all fields in Catalyst that are a part of the dependent picklist.
FAQ
Q. Can I delete a synced field?
A. Yes, you can delete a synced field that has no dependencies. If you receive an error, even if the field has no dependencies, please reach out to our Support team.
Q. I use a different currency than dollars, but I am seeing the $ symbol in Catalyst. Can I change that?
A. At this time, the field data (for each account, opportunity, contact) will populate in Catalyst based on what is provided by your Salesforce instance. The $ symbol is currently the default currency symbol within the platform and cannot be changed. This means that all ARR values and aggregate totals at the top of segments will only display the $ symbol, regardless of currency being used in Salesforce. No currency conversion is taking place.
Q. I mapped a Salesforce formula to a Catalyst field, but the data doesn't appear to be syncing on a regular basis. Why?
A. Catalyst supports Salesforce formula fields as synced fields; however, your teams may need to manually trigger an update to Catalyst when these field values are changed in Salesforce.