Collaborate more effectively and improve processes by connecting the data across your
Salesforce orgs. With the cross-org adapter, Salesforce Connect uses Lightning Platform REST API
calls to access records in other Salesforce orgs. Nevertheless, setup is quick and easy with
point-and-click tools.
Required Editions
Available in: both Salesforce Classic
and Lightning Experience (not for high-data-volume external objects)
Available in: Developer Edition
Available for an extra cost in:
Enterprise, Performance, and Unlimited Editions
Your users and the Lightning Platform interact with other orgs’ data via external objects.
The cross-org adapter for Salesforce Connect converts each of those interactions into a
Lightning Platform REST API call.
Suppose that you store your inventory of products in one Salesforce org. You want your
regional and local branch offices, who have their own orgs, to see the latest information
about your stock. With the cross-org adapter for Salesforce Connect, those other organizations
can easily access your data while respecting access restrictions that you control.
The cross-org adapter makes a Lightning Platform REST API call each time that:
A user clicks an external object tab for a list view.
A user views a record detail page of an external object.
A user views a record detail page of a parent object that displays a related list of child
external object records.
A user performs a Salesforce global search.
A user creates, edits, or deletes an external object record.
A user runs a report.
The preview loads in the report builder.
An external object is accessed via flows, processes, APIs, Apex, SOQL, or SOSL.
You validate or sync an external data source.
To set up Salesforce Connect with the cross-org adapter, you use only point-and-click
tools.
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.