Map Salesforce and Account Engagement Custom Fields
To allow syncing, map prospect and account custom fields.
Required Editions
| User Permissions Needed | |
|---|---|
| To map fields: | Account Engagement Administrator role |
Keep these considerations in mind when mapping fields.
- Before you can map custom fields, create the corresponding custom field in Account Engagement.
- If a Salesforce field is already mapped, it doesn’t display in the dropdown.
- If your Salesforce connector user doesn't have visibility to the Salesforce field, it doesn't display in the dropdown.
- Custom field mapping isn’t case sensitive. For example, the two custom fields Account_Type and account_type on the contact record must map to the same field on the prospect record.
- To map a custom field on both the lead object and contact object to the same Account Engagement field, the API name of the Salesforce fields must be identical.
- Account Engagement fields don’t sync with lookup or geolocation Salesforce field types. Learn how sync behavior works.
- Don’t map number type fields to Salesforce phone type fields. Phone fields contain non-number characters and don’t sync correctly. Instead, map Salesforce phone type fields to text type fields.
-
Open the Prospect Fields page.
- In Account Engagement, select Admin | Configure Fields | Prospect Fields.
- In the Lightning app, select Account Engagement Settings | Object and Field Configuration | Prospect Fields.
- From the Salesforce Field Name dropdown, choose the field you want to map.
- To sync field setting changes from Salesforce, select Use pre-defined values (for checkboxes, radio buttons, drop downs, and multi-selects).
- (Optional) Edit sync behavior.
Repeat these steps for each custom field you want to sync.
Note Mapping an Account Engagement custom field with a Salesforce field doesn’t trigger a sync
with the CRM.
Did this article solve your issue?
Let us know so we can improve!
