External Data Source
A Salesforce configuration that defines how to connect to an external system (like SAP, SharePoint, or a custom database) via Salesforce Connect or OData, enabling external objects to display data from outside Salesforce without copying it.
Definition
A Salesforce configuration that defines how to connect to an external system (like SAP, SharePoint, or a custom database) via Salesforce Connect or OData, enabling external objects to display data from outside Salesforce without copying it.
In plain English
“An External Data Source is a Salesforce configuration that tells Salesforce how to connect to data living outside Salesforce, like SAP or SharePoint. With it, you can show that external data inside Salesforce as if it were stored there, without actually copying it.”
Worked example
When Coppermoor Capital wants to expose data from their on-prem SAP system inside Salesforce, the integration team configures an External Data Source in Setup pointing at SAP's OData endpoint. The External Data Source defines the connection (URL, authentication, refresh interval); from there, the team creates External Objects backed by it. Sales reps see SAP order data as Related Lists on the Account page - fetched live via Salesforce Connect on each page render. The External Data Source is the connection definition; the External Objects are the user-facing surfaces that consume it.
Why External Data Source matters
An External Data Source is a Salesforce configuration that defines how to connect to an external system through Salesforce Connect or OData. It specifies the connection details (URL, authentication, protocol) for accessing data in systems like SAP, SharePoint, custom databases, or other Salesforce orgs. Once configured, the External Data Source enables the creation of External Objects, which display the external data inside Salesforce without storing it locally.
External Data Sources are key to integration scenarios where you want to surface external data in Salesforce without ETL or copying. The data stays in the source system and is fetched on demand when users view records, ensuring it's always current. This is particularly valuable for large datasets that would be impractical to copy, for systems that are the authoritative source of truth, and for scenarios where data residency requirements prevent copying. Salesforce Connect supports several adapter types: OData 2.0, OData 4.0, cross-org (for connecting Salesforce to Salesforce), and custom Apex adapters for systems that don't speak OData.
How to create External Data Source
External Data Sources are the connection records that define how Salesforce reaches an external system — URL, authentication, protocol. Required setup before External Objects can be created. Salesforce Connect supports OData 2.0/4.0, Salesforce-to-Salesforce cross-org, and custom Apex adapters.
- Confirm Salesforce Connect is licensed
Required for non-Salesforce sources. Salesforce-to-Salesforce cross-org is included in many editions.
- Open Setup → External Data Sources
Setup gear → Quick Find: External Data Sources → External Data Sources.
- Click New External Data Source
Top-right.
- Set Label, Name, Type
Type drives the protocol — OData 2.0 / OData 4.0 / Salesforce / Custom (Apex Adapter).
- Configure URL
Endpoint URL of the external system. For OData, the service root URL.
- Configure Authentication
Anonymous / Per-User / Named Principal. Named Principal uses one identity for all users; Per-User requires each user to do their own OAuth dance.
- For Named Principal: configure the credential
Username / password, OAuth tokens, or Named Credential reference.
- Save → click Validate and Sync
Validate tests the connection. Sync auto-creates External Objects representing each external entity / table.
- Object Manager → External Objects → review the synced objects
Verify field mappings, add Indirect / External Lookups.
Required.
Required. Locked after Save.
Required.
Required.
- Authentication mode is critical. Per-User requires each user's individual OAuth — high friction for service-account integrations. Named Principal is easier but uses one identity for everyone.
- Validate and Sync auto-creates External Objects from the external schema. Re-syncing after schema changes can produce surprises — review changes before accepting.
- Connection failures often show as opaque "unable to connect" errors. Test from a network that can reach the external system; check that the user has access to all fields the data source returns.
How organizations use External Data Source
Configured an External Data Source pointing to their ERP system so order data appears in Salesforce as External Objects without being copied. The data stays current automatically.
Uses cross-org External Data Sources to display data from a sister Salesforce org in their main org, avoiding the need for data sync between the two.
Built a custom Apex adapter External Data Source for a legacy system that doesn't speak OData, giving users access to that data inside Salesforce.
Trust & references
Straight from the source - Salesforce's reference material on External Data Source.
- Define an External Data Source for Salesforce ConnectSalesforce Help
- Work with External Data SourcesSalesforce Help
Test your knowledge
Q1. What is an External Data Source?
Q2. What feature uses External Data Sources?
Q3. When are External Data Sources the right choice?
Discussion
Loading discussion…