Sync Considerations for Salesforce Connect OData Adapters
When you validate and sync an external data source of type OData 2.0, 4.0, or 4.01, some special behaviors and limitations apply.
Required Editions
| Available in: both Salesforce Classic and Lightning Experience (not for high-data-volume external objects) |
Available in: Developer Edition Available for an extra cost in: Enterprise, Performance, and Unlimited Editions |
Syncing always enables search on the external object when search is enabled on the external data source, and vice versa.
If a Synced check mark appears, your org has an external object whose object name matches the table name. If you select the table 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) associates it with a table column name (for example,Email). - 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 table column names.
If no Synced check mark appears, and you sync the table, a new external object is created in your org. The new external object’s object name matches the table name.
For example, if the table name is changed on the external system to no longer match the object name of the external object, syncing that table creates a new external object in Salesforce. We recommend that you change the object name of the existing external object to match the new table name on the external system before you sync that table.
Also review the considerations that apply to all Salesforce Connect adapters.
