Considerations for Custom Mapping of Data.com and Salesforce Fields | Salesforce
Considerations for Custom Mapping of Data.com and Salesforce Fields
Custom mappings put Data.com values in the Salesforce account, contact, and lead fields where you want those values. Before mapping fields, make sure you understand how mapping works, what preparations to make, and what kind of results you should expect.
Available in: Salesforce Classic
Available with a Data.com Prospector license in: Contact Manager (no Lead object), Group, Professional, Enterprise, Performance, and Unlimited Editions
Available with a Data.com Clean license in: Professional, Enterprise, Performance, and Unlimited Editions
Not all Data.com fields are available for all Salesforce fields. To be mappable, the new Salesforce field must be the same data type as the default field. For example, the Description field can be mapped to a long text area field with 1,000 characters or more.
Custom field mappings apply when:
Data.com records are added to Salesforce
Salesforce records are matched with Data.com records and cleaned either manually or with automated jobs
Before you map fields, make sure you understand these potential outcomes and the related actions you should take.
Mapping fields or updating mappings forces a full sync with Data.com: all records of enabled CRM objects (accounts, contacts, and leads) are updated, even if no records have changed.
Data.com field mappings may conflict with any Salesforce field customizations (such as approvals, workflow rules, or Apex triggers) you use for accounts, contacts, leads, or D&B Company records. Review and edit your customizations as needed so they will work with the values supplied by your mappings.
You can skip mapping individual Data.com fields, but values for skipped fields won't be added, exported, or considered when we calculate a record’s clean status.
Skipping or changing mappings for fields used to match Salesforce and Data.com records may change some records’ clean status to Not Found.
For account records, skipping or changing the mapping for the D-U-N-S Number field will cause all account jobs to use the Data.com matching service, rather than the D-U-N-S Number field, to rematch account records.
If you map fields and also set Clean job preferences to flag, auto-fill, or overwrite Salesforce fields, you’ll see any custom-mapped fields when you set those preferences. Default mappings (such as from the Data.com Phone field to the Salesforce Phone field) do not appear.
If you export Data.com search results, the column headers in your Excel file will show the mapped field names. For example, if you map the Data.com Phone field to the Contact object’s Mobile field, you’ll see a header called “Mobile” for contacts, not “Phone”.
If you map Data.com fields that do not have values, some Salesforce records might revert to Not Found clean status.
If you map a Data.com field to a custom Salesforce field, the custom field’s label will appear on the Clean comparison page.
If you want to track changes to field mappings, you’ll find them in the Setup Audit Trail. From Setup, enter View Setup Audit Trail in the Quick Find box, then select View Setup Audit Trail.
Default Data.com-to-Salesforce Field Mappings When you add records with Data.com Prospector or update records with Data.com Clean, some Salesforce fields get values from Data.com. Salesforce admins can customize these field mappings.