Who can use this feature?
- All roles with access level "high"
- Available on all plans
Non-synced fields allow your team to read and edit data that is only local to Catalyst. Local fields do not sync with Salesforce, unless configured to do so at a later time.
Supported field types
Non-synced fields are available for any of these input types:
- Text (255 characters max)
- Text area (4K characters max)
- Text area (long) (16K characters max)
- Rich text area (16K characters max)
- Integer
- Decimal
- Picklist
- Date and time
- True/false
- Percent
- Date
- Catalyst user reference
- Catalyst account reference
- Catalyst contact reference
Character limits for local Catalyst text-based fields do not apply to synced fields (Salesforce).
Create new Catalyst local fields
User created "data warehouse" fields are new fields you need to create in Catalyst that you want to map with your connected data source. Supported fields types include: Text, numbers, Booleans, and ISO 8601 formatted dates in a comma delimited CSV + timestamp with time zone.
- In Catalyst, navigate to Settings > Object Configuration.
- Open one of your objects (e.g., accounts) that is related to a configured data source.
- Click + Add Field.
- Choose Non-Synced Field, and click Next.
- Enter the field details:
- Choose the input type for how the field will be displayed.
- Choose a unique name for the field.
- Optionally provide a description.
- Click Create.
Within the object, you can view your new field.
Enable sync with Salesforce
For any non-synced (local) Catalyst field, you can optionally enable sync with Salesforce. This option is available after a local field has been created.
A common use case for this option is if your Salesforce operational team has decided to create a Salesforce field to correspond to the field in Catalyst so that you can push that data into Salesforce. Refer to the following considerations:
- Local Catalyst reference fields cannot be synced to Salesforce
- When turning on syncing, only Salesforce fields with the same field type will populate in the dropdown
- When syncing a local picklist, the picklist and values in Salesforce must be identical to the picklist in Catalyst, including the Unique IDs/API names. The picklist type must match as well (multi-select vs regular picklist)
- When sync is turned on, existing Catalyst data will be overwritten by Salesforce if a Salesforce field value is present or if the field is read-only.
We recommend exporting field data from Catalyst before turning on sync if you would like to retain the Catalyst field data, but are uncertain if there is data on this field in Salesforce. This will ensure you have a record of the previous Catalyst field data as a backup.