Apex Developer Guide

Getting Started
Writing Apex
Ways to Invoke Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Approval Processing
Authentication
Chatter Answers and Ideas
Chatter in Apex
Moderate Chatter Private Messages with Triggers
Moderate Feed Items with Triggers
Communities
Email
Platform Cache
Salesforce Knowledge
Salesforce Connect
Salesforce Connect
Writable External Objects in Salesforce Connect
Writable External Objects
Considerations for Writable External Objects
Get Started with the Apex Connector Framework
Key Concepts About the Apex Connector Framework
Considerations for the Apex Connector Framework
Apex Connector Framework Examples
Salesforce Reports and Dashboards API via Apex
Force.com Sites
Support Classes
Territory Management 2.0
Visual Workflow
Integration and Apex Utilities
Finishing Touches
Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Considerations for Writable External Objects

Understand the limits and considerations for writable external objects in Salesforce Connect. Creating, updating, and deleting external object records aren’t perfect processes because the data is stored outside your Salesforce org.
  • 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.
  • Writable external objects aren’t available for high-data-volume external data sources.
  • Queued changes to the external data execute over time, so external object records that are read successively can contain different data.