Purpose:
The purpose of this article is to provide information to Outreach Admins regarding Advanced Field Mapping with Outreach.
Intended Audience:
- Outreach Admins
Notes:
- The following information applies to both Salesforce and Microsoft Dynamics instances.
- While configuring CRM Plugin settings, occasionally there is a need to use Advanced Field Mappings to get information to update correctly between Outreach and the CRM.
- If a field is already mapped and syncing, you don't need to adjust these settings. Outreach does not recommend adding/removing advanced mappings to/from existing field mappings, as this could cause records of that object type to stop syncing.
- When the CRM plugin is initially created in your account, Outreach automatically assigns advanced field mapping settings to the Owner (see example below), Lead Status, Account, and Governance Role fields.
Advanced Field Mappings:
Advanced Mapping Definitions
| Option | Definition |
|---|---|
| Skip Empty Values When Sending Data to a CRM | This setting prevents users from overwriting data in the CRM with a blank value. If deselected, blank data can be pushed to the CRM. Example: If a user removes a Prospect's phone number in Outreach, we do not want to overwrite the existing phone number from the Lead or Contact with a blank value in the CRM. |
| Skip Empty Values When Loading Data from a CRM | This setting prevents users from overwriting data in Outreach with a blank value; if unchecked, blank data can be pulled from the CRM to Outreach. Example: If a Lead's email address is deleted in the CRM, this option will prevent the existing email address of the Prospect in Outreach from being overwritten with a blank value. |
| External Empty Placeholder | Allows Outreach to substitute a blank value with text in the event a blank value is attempting to push to the CRM. Example: A validation rule on the Lead object in the CRM requires all Leads to have a last name. If the last name field is blank in Outreach, the platform can replace the blank value with "TBD" when pushing to the Lead Record to satisfy the validation rule and get the Prospect's record and activity into the CRM until that field can be populated with the applicable information. |
| Internal Empty Placeholder | Allows Outreach to substitute a blank value with text in the event a blank value is attempting to pull from the CRM to Outreach. Example: If you would like to map the SDR Owner, AE Owner, and CSM Owner to custom Outreach fields, you would need to check this box and change the external mapped type to user. (Described below.) |
| External Mapped Field |
Provides the list of lookup field types that Outreach can map to. Note: This must be enabled when mapping a lookup field in a CRM to an object field in Outreach. |
| External Mapped Type | Provides the list of lookup field types that Outreach can map to. Example: If you're trying to map an Owner field, you will need to enable the Mapped Field option and set the External Mapped Type to User. |
| Look for name instead of record ID |
Enables Outreach to lookup the Record Name rather than the Record ID in the CRM. Note: This field must checked when mapping a lookup field from a CRM to a custom field (or text field) in Outreach. |
| Display Name instead of record ID |
Enables Outreach to display the Record Name rather than the Record ID from a CRM. |
Additional Resources:
Outreach Standard Task Mapping
© 2023 Outreach.io