Record IDs and External IDs for External Objects in Salesforce
Connect—Cross-Org Adapter
External object record IDs are derived from the corresponding record IDs in the
provider organization. External ID values in external object records match the record IDs in the
provider organization.
Required Editions
Available in: both Salesforce Classic and Lightning Experience
Available in: Developer Edition
Available for an extra cost in:
Enterprise, Performance, and Unlimited Editions
Each object in Salesforce has an object ID with a key prefix as the first three characters.
When an external object is created, it’s assigned a unique key prefix.
Each external object record has a record ID that uses the same key prefix as the external
object ID. The rest of the external object record ID matches the original record ID that’s in
the provider organization, excluding its original key prefix.
Each record ID that comes from the provider organization becomes a case-insensitive
18-character alphanumeric string in the subscriber organization.
The original record ID is available in the subscriber organization as the value of the
External ID standard field on the external object record.
Each external object has an External ID standard field. Its values
uniquely identify each external object record in your org. When the external object is the
parent in an external lookup relationship, the External ID standard field is used to identify
the child records.
Example You sync the provider organization’s Account object, and the subscriber organization’s
Account__x object is assigned the key prefix x00. An account in the provider organization with the ID
001B0000003SVC7IAO appears in the subscriber organization with the ID x00B0000003SVC7IAO and
the external ID 001B0000003SVC7IAO.
We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required Cookies
Always Active
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional Cookies
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising Cookies
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.