Sync an External Data Source for Salesforce Connect

Syncing fails if it causes your org to exceed 200 external objects. Syncing also fails if it tries to create an external object with an API name that conflicts with an existing object in the org. In such cases, determine whether the existing object is needed.

• If the object isn’t needed, delete that object, and sync again.
• If the object is needed, change the API name of the existing object to no longer conflict with the table that you're trying to sync. However, if the existing object is an external object that was previously synced, you can’t resync it. Manually update the external object and its fields as needed for schema changes on the external system.

Tip We recommend that you create your external data sources and external objects in a Developer Edition org. Then use managed packages to deploy the external data sources and external objects to your other orgs. Doing so prevents your external object names from conflicting with other objects in your org by applying a namespace prefix.

When an external object is created via syncing, its Deployment Status is set to In Development. When you’re ready to expose the external object to users, set the status to Deployed.

If the external system’s schema changes, the modifications aren’t automatically synced to your Salesforce org. To reflect the changes in the external system, resync the objects. After resyncing, all users who have the same profile as the user who initiated the resync are granted field-level access to the external objects. When you resync an external object:

• The Display URL Reference Field is set to None.
• If a custom field has the Is Name Field attribute, the attribute is removed. The External ID standard field is used as the name field of the external object.
• The Deployment Status doesn’t change.

To understand how syncing affects relationship fields on external objects, see Relationships on External Objects.