Understanding the Cross-Org Adapter Org Configuration
This Page
All Documentation
The high-level setup is split between two orgs. We recommend following this complete example end to end. You can then adapt the same patterns for your target use case.
Publisher org (Acme Order Management): the org that contains the data you want to access; stores Order__c custom records.
Subscriber org (Acme Service Cloud): the org you’re working in. After you set up the adapter, publisher Order__c records appear in the subscriber org as the Order__x external object. An indirect lookup on Customer Email links each order to its Account, so service agents can see a customer’s orders in real time on the Account record.
Setup Tasks in the Publisher Org
Obtain a Salesforce org.
Create the Order custom object and sample data.
Create an external client app.
Configure OAuth scopes and flow settings.
Note the consumer key and consumer secret.
Setup Tasks in the Subscriber Org
Obtain a Salesforce org with a Salesforce Connect license.
For browser flow auth only: Create an external auth identity provider (XIDP).
Create an external credential.
Create a named credential.
Create an external data source.
Validate and sync external objects.
Surface order data on the Account page layout.
Prerequisites
A Salesforce Connect license on the subscriber org. This license is an add-on with limits on the number of external data sources and objects in the org. See General Limits for Salesforce Connect. Contact your Salesforce account executive to verify whether you have a Salesforce Connect license.
Admin access on both the subscriber and publisher orgs.