Force.com Apex Code Developer's Guide

Getting Started
Writing Apex
Ways to Invoke Apex
Invoking Apex
Apex Transactions and Governor Limits
Using Salesforce Features with Apex
Actions
Approval Processing
Chatter Answers and Ideas
Chatter in Apex
Moderate Chatter Private Messages with Triggers
Communities
Email
Salesforce Knowledge
Lightning Connect
Lightning Connect Overview
Get Started with the Apex Connector Framework
Key Concepts About the Apex Connector Framework
Considerations for the Apex Connector Framework
Apex Connector Framework Examples
Salesforce1 Reporting API via Apex
Force.com Sites
Support Classes
Territory Management 2.0
Visual Workflow
Integration and Apex Utilities
Finishing Touches
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 Lightning Connect custom adapters with the Apex Connector Framework.
  • Your DataSource.Provider class must declare the DataSource.Capability.ROW_QUERY capability. Otherwise, the sync method on the DataSource.Connection class might not work as expected.
  • 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.
  • 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 Lightning Connect are subject to the same limitations as any other Apex code. For example:
    • All Apex governor limits apply.
    • Apex callouts aren’t allowed after data manipulation language (DML) operations in the same transaction. This means that within the same transaction, you can't update a Salesforce record and then do an Apex callout.