Writable External Objects Considerations for Salesforce Connect—OData 2.0 and 4.0 Adapters | Salesforce
Some special behaviors and limitations affect writable external objects that are associated with OData adapters for Salesforce Connect.
|Available in: both Salesforce Classic and Lightning Experience|
|Available in: Developer Edition|
Available for an extra cost in: Enterprise, Performance, and Unlimited Editions
- An external object custom field associated with an OData complex type on the external system is always read only, even if the external object is writable.
- Writable external objects aren’t available for high-data-volume external data sources.
- Make sure that the OData producer supports these HTTP verbs: POST, PUT, MERGE, PATCH, and DELETE.
- When a user edits fields on an external object record from the Salesforce user interface, Salesforce Connect sends an HTTP POST request to the external system. That POST request includes all the external object’s fields, including the fields that the user didn’t change.
- If an external object record is edited from the API, only the specified fields are included in the HTTP POST request.
- If your external system requires write operations to specify values for entity keys, ensure that External ID standard field values and entity key values don’t contradict each other. For each write operation, include either the External ID standard field value or the custom field values that form the entity key, but never both.
Also review the considerations that apply to all Salesforce Connect adapters.