OData Producer
In Salesforce Connect, an external system that exposes data through OData protocol endpoints, allowing Salesforce to consume and display that external data as external objects without storing it locally.
Definition
In Salesforce Connect, an external system that exposes data through OData protocol endpoints, allowing Salesforce to consume and display that external data as external objects without storing it locally.
In plain English
“An OData Producer is an external system that exposes data through OData protocol endpoints. Salesforce Connect uses OData Producers to consume external data and display it as External Objects in Salesforce, without copying or storing the data locally.”
Worked example
Highland Steel keeps mill-floor inventory in an on-prem SAP system that finance and operations both depend on. Rather than copying that inventory into Salesforce nightly, the integration team stands up an OData Producer in front of SAP - a service that exposes the inventory tables through OData v4 endpoints. Salesforce Connect points at the Producer, generates External Objects for the inventory entities, and sales reps see live SAP inventory levels on the Account page exactly as they see native Salesforce data - except nothing is stored in Salesforce. Each query hits the Producer in real time, so inventory shown in Salesforce is always seconds-fresh, and if SAP goes down the External Objects surface as unavailable instead of serving stale data.
Why OData Producer matters
In Salesforce Connect, an OData Producer is an external system that exposes data through OData protocol endpoints, allowing Salesforce to consume and display that external data as external objects without storing it locally. OData (Open Data Protocol) is an open standard for building and consuming RESTful APIs that work with structured data. An OData Producer is the server side: a system that publishes data via OData endpoints that Salesforce Connect can read.
OData-based external objects are valuable when you want to surface external data in Salesforce without the operational overhead of data sync. The data lives in the source system (the OData Producer) and Salesforce queries it on demand when users access the external objects. This is appropriate for reference data, large datasets that don't need to be in Salesforce, and scenarios where the source of truth must remain external. The trade-off is that querying is slower than local data access and depends on the external system being available.
How organizations use OData Producer
Connected Salesforce to their ERP system through an OData Producer interface, surfacing order data as External Objects without sync overhead.
Uses OData-based external objects for reference data that lives in another system but needs to be visible in Salesforce.
Treats Salesforce Connect with OData as one option among several integration approaches, picking based on data access patterns.
Trust & references
Straight from the source - Salesforce's reference material on OData Producer.
- Define an External Data Source for Salesforce Connect ODataSalesforce Help
Test your knowledge
Q1. What is an OData Producer?
Q2. What does Salesforce do with OData Producer data?
Q3. What's a trade-off?
Discussion
Loading discussion…