Best Practices for Mapping Fields in Salesforce to Salesforce | Salesforce
Best Practices for Mapping Fields in Salesforce to Salesforce
When you subscribe to a field in Salesforce to Salesforce, you need to map it to a field in your organization. This lets updates to that field sync for all shared records. Before you map fields, take a look at these important best practices.
Available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions
This information applies to standard Salesforce to Salesforce connections. If you’re mapping fields for a replication connection as part of Organization Sync, some of this information may not apply.
When subscribing to fields, select Auto-Map Fields to automatically map your business partner's fields to your fields. After you select this option, click Save for your changes to take effect.
For any unmapped field, Salesforce checks if the field's API name matches that of any of your fields. If there are no matches, Salesforce checks for matching field labels. If Salesforce still can’t find a match, --None-- is selected.
Selecting Auto-Map Fields doesn’t overwrite previous selections, and deselecting it doesn’t affect fields that were mapped previously.
The following standard fields are automatically mapped:
Account: Account Name, and, if you are using person accounts, Last Name
Attachment: Body, Content Type, File Name
Case Comment: Body and Published
Contact: Last Name
Custom Object: Name
Lead: Last Name and Company
Opportunity: Name, Closed Date, and Stage
Product: Product Name
Opportunity Product: Quantity, Sales Price
Mapping Picklist Fields
If a picklist value is mapped to --None--, and your business partner enters a picklist value, your picklist field will be set to the same value. For example, if you subscribe to the Lead Status picklist, and your business partner has the value Internal in that picklist, your record will have a lead status of Internal.
To convert a custom field to a picklist field, stop publishing the field, change the field type, then publish the field again.
When mapping picklist fields, If the subscribed org has the field with property Strictly enforce picklist values enabled, and the publishing org has Strictly enforce picklist values disabled, the field is not available for mapping on the subscribing org.
Mapping Currency Fields
If you map a currency field, and a record shared by your connection uses a currency that your organization hasn’t enabled, that currency field won’t be updated when your organization auto-accepts the record. If you’re manually accepting the record, the currency is updated only if your organization uses the same currency as the record.
For example, suppose your connection has shared an opportunity with you. Your organization uses the Euro only. Your connection updates the opportunity amount to $300. The opportunity amount won’t update in your record because your organization doesn't support the U.S. Dollar.
If you map a currency field and either you or your connection changes the currency on a record containing that field, updates you make to the field will no longer be propagated to the other organization, and updates your connection makes to the field won’t be reflected in your organization.
You can map roll-up summary fields to currency fields with the same currency type. For example, a roll-up summary with the currency type U.S. Dollar can be mapped to a currency field that uses the U.S. Dollar.
Mapping Quantity and Revenue Schedules
If Quantity Schedules or Revenue Schedules are enabled in your connection's organization and you subscribe to the Products object from that connection, you must subscribe to the following fields and map them to matching fields in your organization.
Type of Schedule
Fields to Map
Number of Quantity Installments
Quantity Installment Period
Quantity Schedule Type
Number of Revenue Installments
Revenue Installment Period
Revenue Schedule Type
Mapping Different Field Types
Person account fields should be mapped only to person account fields, and business account fields should be mapped only to business account fields.
If your connection is using person accounts and you aren’t, the person account field Last Name is used as the Account Name when your connection shares a person account record with you. If you enable person accounts, you are automatically subscribed to Last Name. Any changes to Last Name and Account Name are synced.
You can’t map a standard number field to a custom number field.
You can map lookup fields to text fields that have a length of 80 or more characters. If your connection edits a lookup field that you mapped to a text field, the text field will be updated with their changes.
You can map auto-number fields to text fields that have a length of 30 or more characters.
You can map formula fields to fields of the same data type; for example, a formula field that has a number data type can be mapped to a field with a number data type. If a formula field is a text data type, it can be mapped to a text field with a length of 80 or more characters. Conversely, fields can’t be mapped to formula fields; for example, a formula field with a currency data type can be mapped to a currency field, but a currency field cannot be mapped to a formula field. System audit fields are not supported.
Unsubscribing to Fields
You are automatically unsubscribed from a field if:
Your business partner stops publishing the field
You delete a custom field that is mapped to a published field
The field type of a custom picklist or custom multi-select picklist is changed (for example, if a custom picklist is changed to a text field)