Writable External Objects Considerations for Lightning Connect—All Adapters | Salesforce
Understand the limits and considerations for using Lightning Connect to create, update, and delete data that’s stored outside your Salesforce org.
|Available in: both Salesforce Classic and Lightning Experience|
|Available in: Developer Edition|
Available for an extra cost in: Enterprise, Performance, and Unlimited Editions
- The external system handles write conflicts, so we can’t guarantee that all write operations that are initiated from within Salesforce are applied.
- Write operations that are initiated from different contexts can occur in varying order.
- The API can’t save changes to an external object and a standard or custom object within the same transaction.
- Depending on how the external system executes write operations from Salesforce, 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.
- When a user or the Force.com platform edits a custom field on an external object record, leading and trailing spaces are removed from the field value.
- When a user tries to edit an external lookup or indirect lookup relationship field, a lookup dialog isn’t available for selecting the parent record.
- To edit an external lookup relationship field, manually enter the value of the External ID standard field for the parent record.
- To edit an indirect lookup relationship field, manually enter the value of the target field of the parent record. The target field is the custom field with External ID and Unique attributes that was selected when the indirect lookup relationship was created. To determine related records, Salesforce matches target field values against the values of the indirect lookup relationship field on the child object.
Also review the considerations for each Lightning Connect adapter that you use.