You are here:
Best Practices for Mapping Fields in Salesforce to Salesforce
When you subscribe to a field in Salesforce to Salesforce, you map it to a field in your org. This mapping syncs updates between the fields for all shared records. Before you map fields, look at these important best practices.
Required Editions
| Available in: Contact Manager, Group, Professional, Enterprise, Performance, Unlimited, and Developer Editions |
Important Salesforce to
Salesforce is scheduled for retirement as of Spring ’27. See Salesforce to Salesforce Retirement.
Important This information applies to standard Salesforce to Salesforce
connections.
Auto-Mapping Fields
- When subscribing to fields, select Auto-Map Fields to automatically map your business partner's fields to your fields. Click Save for your changes to take effect.
- For unmapped fields, Salesforce checks if the field's API name matches any of your fields. If no match exists, 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: Subject
- 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
- Task: Subject
- 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 is 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 gets a lead status of Internal.
- To convert a custom field to a picklist field, stop publishing the field, change the field type, and publish the field again.
- For a picklist field to be subscribable, the publishing and subscriber orgs' picklist field must:
- Both restrict or both not restrict to values defined in the value set
- Use the same API name for the picklist field
Mapping Currency Fields
- When you map a currency field, and a record shared by your connection uses a
currency that your org hasn’t enabled:
- The shared record’s currency field isn’t updated when your org auto-accepts the record
- If you’re manually accepting the record, the currency is updated only if your org uses the same currency as the record
For example, suppose that your connection has shared an opportunity with you. Your org uses only the euro. Your connection updates the opportunity amount to US$300. The opportunity amount isn’t updated in your record because your org doesn't support the U.S. dollar.
- When you map a currency field and either you or your connection changes the currency on a
record containing that field:
- Updates that you make to the field are no longer propagated to the other org
- Updates that your connection makes to the field aren’t reflected in your org
- You can map roll-up summary fields to currency fields with the same currency type. For example, a roll-up summary field 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 org and you
subscribe to the Products object from that connection, you must:
- Subscribe to all fields in the relevant Fields to Map column
- Map each field to the matching fields in your org
Type of Schedule Fields to Map Quantity Schedule - Number of Quantity Installments
- Quantity Installment Period
- Quantity Schedule Type
Revenue Schedule - Number of Revenue Installments
- Revenue Installment Period
- Revenue Schedule Type
Mapping Different Field Types
- Only map person account fields to person account fields, and business account fields 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 is updated with their changes.
- You can map auto-number fields to text fields that have 30 or more characters.
- You can map formula fields to fields of the same data type. For example, you can map a formula field that has a number data type to a field with a number data type. If a formula field is a text data type, you can map it to a text field of 80 or more characters.
- You can’t map fields to formula fields. For example, you can map a formula field with a currency data type to a currency field, but you can’t map a currency field 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)
General Mapping Best Practices
- When publishing fields, consider sending your business partner information about the fields. This information helps them to create a mapping strategy that makes sense for your program.
- Translate your published custom field names into the languages that your partners use.
- If you’re using person accounts, and your connection has not enabled person accounts, the person account Last Name is used as the Account Name when you share a record. If your connection enables person accounts, they are automatically subscribed to Last Name. Any changes to Last Name and Account Name are synchronized.
- If you want to publish the Middle Name, Informal
Name, and Suffix fields on contacts, either:
- The fields must be enabled in both your org and your partner’s org
- Your partner’s org must be configured to auto-accept contacts
Did this article solve your issue?
Let us know so we can improve!
