Loading
Salesforce now sends email only from verified domains. Read More
Extend Salesforce with Clicks, Not Code
Table of Contents
Select Filters

          No results
          No results
          Here are some search tips

          Check the spelling of your keywords.
          Use more general search terms.
          Select fewer filters to broaden your search.

          Search all of Salesforce Help
          Set Up Salesforce Connect to Access External Data with OData Adapters

          Set Up Salesforce Connect to Access External Data with OData Adapters

          Let users view and search data that’s stored outside your Salesforce org, such as data in an enterprise resource planning (ERP) system.

          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

          User Permissions Needed
          To create and edit external data sources: Customize Application
          To create and edit external objects: Customize Application
          To define or change object-level help: Customize Application
          To create and edit custom fields: Customize Application
          To edit permission sets and user profiles: Manage Profiles and Permission Sets
          To edit another user’s authentication settings for external systems: Manage Users

          Setting up Salesforce Connect with an OData 2.0, 4.0, or 4.01 adapter involves these high-level steps.

          1. Define an external data source of type Salesforce Connect: OData 2.0 or Salesforce Connect: OData 4.0. or Define an external data source of type Salesforce Connect: OData 4.01.
            If your external system hosts multiple services, create an external data source for each service endpoint. Each service endpoint points to an OData service root URL and can expose collections of entities. For example, you’d create a separate external data source for each of these service endpoints.
            • http://services.example.org/Warehouse.svc
            • https://services.example.org/Payroll.svc
          2. Create the external objects.
            Perform this task only if you don’t sync to automatically create the external objects. Create an external object for each external data table that you want to access from your Salesforce org.
          3. Add custom fields and relationships to the external objects.
            Create relationships between objects. If you didn’t sync to automatically create the external objects and their fields, create a custom field for each external table column that you want to access from your Salesforce org.
          4. Verify access to external object data.
            Check that expected user and code interactions with the external objects work, including sorting and filtering search and query results.
            Tip
            Tip After you configure an external data source, run the validator tool on each external object to test and troubleshoot its connections. The tool tests for ID uniqueness and the ability to sort and filter results.
          5. Enable user access to external objects.
            Grant object permissions through permission sets or profiles.
          6. Enable user access to the fields on the external objects.
            Grant field permissions through permission sets or profiles.
          7. If the external data source uses per-user authentication:
            1. Let users authenticate to the external system.
              Grant users access to authentication settings for the external data source through permission sets or profiles.
            2. Set up each user’s authentication settings.
              You or your users can perform this task.
              Tip
              Tip Train your users on how to set up their authentication settings for external systems. Make sure that they know which credentials to enter for each external system. If you’re using OAuth 2.0, test the OAuth flow for potentially confusing prompts or redirects, and train your users as needed. OAuth flows vary, depending on your external system, authentication provider, and specified scopes.
           
          Loading
          Salesforce Help | Article