Sync Considerations for Salesforce Connect—Cross-Org Adapter

• Which objects and fields can be synced is determined by the object permissions and field permissions of the provider org’s user whose credentials are defined in the external data source definition. See User Access to External Data in Salesforce Connect—Cross-Org Adapter.
• Only queryable objects can be synced.
• You can’t sync an object whose API name contains 38 or more characters. An external object’s name can’t exceed 40 characters, including the automatically appended __x suffix. See API Names for External Objects and Custom Fields in Salesforce Connect—Cross-Org Adapter.
• These field types aren’t synced.
  • Encrypted text
  • Rich text area
• Global picklist value sets aren’t synced. If a provider org’s picklist field uses a global picklist value set, syncing creates a local picklist field on the subscriber org. A local picklist field has its own set of values.
• Inactive picklist values aren’t synced. If the subscriber org accesses an external object record that contains an inactive picklist value, the inactive value is added to the picklist field on the external object.
• Syncing converts restricted picklists on the provider org into unrestricted picklists on the subscriber org’s external objects.

  We recommend having only unrestricted picklists on external objects, even when they’re associated with restricted picklists on the provider org. Restricted picklists on the provider org block unapproved values from the subscriber org, eliminating the need to restrict picklists on external objects.

• To enable users to change the currency when editing an external object record, add the Currency field to the page layouts. All other synced fields are automatically added to the default page layout.
• Syncing always enables search on the external object when search is enabled on the external data source, and vice versa.
• Hierarchical, lookup, and master-detail relationship fields are synced. However, they become text fields in the subscriber org, and their values appear as IDs, not as record names.

  For example, suppose that we sync the Account object. When we view the Acme Wireless account in the provider org, the value of the Account Owner (Account.OwnerId) field appears as John Smith. When we view the equivalent account in the subscriber org, the value for the (Account__x.OwnerId__c) field appears as 005B00000019eapIAA.

• You can use external lookup relationships in the subscriber org to mirror lookup relationships in the provider org. For each lookup relationship that you want to bring into the subscriber org, sync the parent and child objects. Each lookup relationship field becomes a text field on the subscriber org. Change the field type of the sync-created text field to External Lookup Relationship. When specifying the parent of the external lookup relationship, select the external object that corresponds to the parent object in the provider org.
• The names and labels of synced fields on the subscriber org are derived from the API names—not the labels—of the fields on the provider org. For example, the Account object in the provider org has the Account Owner (OwnerId) standard field. If we sync the Account object, the Account__x.OwnerId__c field in the subscriber org has the label “Owner ID” and the name “OwnerId.”

Important When you select the provider org objects to sync, determine whether check marks appear in the Synced column.

If a Synced check mark appears, the subscriber org has an external object whose object name (for example, Account__x) associates it with the object in the provider org (for example, Account). If you select the object and click Sync:

• The external object is overwritten.
• Any custom field on the external object is overwritten if its API name (for example, Email_c__c) associates it with a field on the provider org (for example, Email__c).
• Any other custom fields on the external object remain as they are, including:
  • Previously synced custom fields whose API names were changed by editing their Field Name values.
  • Manually added custom fields whose API names aren’t associated with fields on the provider org’s object.

If no Synced check mark appears, and you sync the object, a new external object is created in the subscriber org.

For example, the object name is changed on the provider org to no longer be associated with the object name of the external object on the subscriber org. Syncing that object creates a new external object on the subscriber org. We recommend that you change the object name of the existing external object to match the updated object name on the provider org before you sync.

Also review the considerations that apply to all Salesforce Connect adapters.