Apex Developer Guide

Apex Developer Guide
Getting Started with Apex
Writing Apex
Running Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Approval Processing
Authentication
Chatter Answers and Ideas
Chatter in Apex
Moderate Chatter Private Messages with Triggers
Moderate Feed Items with Triggers
Communities
Email
Metadata
Platform Cache
Salesforce Knowledge
Salesforce Files
Salesforce Connect
Salesforce Connect
Apex Considerations for Salesforce Connect External Objects
Writable External Objects
Get Started with the Apex Connector Framework
Key Concepts About the Apex Connector Framework
Considerations for the Apex Connector Framework
Apex Connector Framework Examples
Salesforce Reports and Dashboards API via Apex
Force.com Sites
Support Classes
Territory Management 2.0
Visual Workflow
Integration and Apex Utilities
Debugging, Testing, and Deploying Apex
Apex Language Reference
Appendices
Glossary
PDF

Newer Version Available

This content describes an older version of this product. View Latest

Considerations for the Apex Connector Framework

Understand the limits and considerations for creating Salesforce Connect custom adapters with the Apex Connector Framework.
  • 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.
  • DML operations aren't allowed in the Apex code that comprises the custom adapter.
  • 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.