Considerations for Writable External Objects
Understand the limits and considerations for writable external
objects in Lightning Connect. Creating, updating, and deleting external object records aren’t perfect processes
because the affected data is stored outside the Salesforce
org.
- The Salesforce adapter
for Lightning Connect doesn’t support writable external objects. External objects can be made
writable only when an OData or custom adapter connects the Salesforce org to the
external system that stores the data.
- External objects that are associated with high-data-volume external data sources
can’t be writable.
- If external object records are read shortly after a write operation, they
sometimes don’t reflect recent changes.
- Queued changes to the external data execute over time, so external object
records that are read successively can contain different data.
- The API can’t save changes to combinations of external objects and other types
of objects. It saves only to one or the other at one time.
- The external system handles write conflicts, so we can’t guarantee that all
writes that are initiated from within Salesforce are
applied.
- Writes that are initiated from different contexts can occur in varying
order.