Loading
Upcoming Mandatory Changes to Public Key Infrastructure (PKI)Read More
Salesforce Enforces New Security Requirements in Summer 2026Read More
Extend Salesforce with Clicks, Not Code
Table of Contents
Filter by (0)Add
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
            Search all of Salesforce Help
            Apex Connector Framework Considerations for Salesforce Connect—Custom Adapter

            You are here:

            1. Salesforce Help
            2. Docs
            3. Extend Salesforce with Clicks, Not Code

            Apex Connector Framework Considerations for Salesforce Connect—Custom Adapter

            Understand the limits and considerations for creating a Salesforce Connect custom adapter with the Apex Connector Framework.

            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
            • If you change and save a DataSource.Connection class, resave the corresponding DataSource.Provider class. Otherwise, when you define the external data source, the custom adapter doesn’t appear as an option for the Type field. Also, the associated external objects’ custom tabs no longer appear in the Salesforce UI.
            • DML operations aren’t allowed in the Apex code that comprises the custom adapter.
            • Apex methods with the future annotation aren't supported in an Apex custom adapter. When a future method is invoked, the external callout could cause an error in Salesforce.
            • Make sure that you understand the limits of the external system’s APIs. For example, some external systems accept only requests for up to 40 rows.
            • Apex data type limitations:
              • Double—The value loses precision beyond 18 significant digits. For higher precision, use decimals instead of doubles.
              • String—If the length is greater than 255 characters, the string is mapped to a long text area field in Salesforce.
            • Custom adapters for Salesforce Connect are subject to the same limitations as any other Apex code. For example:
              • All Apex governor limits apply.
              • Test methods don’t support web service callouts. Tests that perform web service callouts fail. For an example that shows how to avoid these failing tests by returning mock responses, see Google Drive™ Custom Adapter for Salesforce Connect .
            • In Apex tests, use dynamic SOQL to query external objects. Tests that perform static SOQL queries of external objects fail.

            See Also

             
            Loading
            Salesforce Help | Article