Writable External Objects in Salesforce Connect

External systems execute write operations initiated from Salesforce and also handle write conflicts, if any.

• It can take some time for changes to external object records to take effect. If you don’t see recent changes when you view or query an external object record, try again later.
• It can’t be guaranteed that all write operations that are initiated from Salesforce are applied in case of write conflicts.

If Salesforce attempts to save changes to an external object and a standard or custom object in the same transaction, an error occurs. As a best practice, we recommend you use a separate transaction to access or modify data in an external system.

Write operations on external object records initiated from different contexts can occur in varying order. When you create, update, or delete external object records via the user interface, processes or flows, operations occur synchronously. When Apex is used to perform external records operations, operations occur asynchronously and an active background queue minimizes potential save conflicts. To monitor an asynchronous job progress, use BackgroundOperation.

Note When a custom field on an external object record is edited, leading and trailing spaces are removed from the field value.