It's common for Salesforce Connect queries of external data to have a large result
set that's broken into smaller batches or pages. You can decide whether to have the paging
behavior controlled by the external system (server-driven) or by the OData adapter for
Salesforce Connect (client-driven).
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
|
By default, the OData adapters for Salesforce Connect use client-driven paging.
Specifically, the OData requests use the $top and
$skip system query options to page through the
result set.
With server-driven paging, the external system determines the page sizes and batch
boundaries. The external system’s paging settings can optimize the external system’s
performance and improve the load times for external objects in your org. Also, the
external data can change while your users or the Lightning Platform are paging through
the result set. Typically, server-driven paging adjusts batch boundaries to accommodate
changing external data more effectively than client-driven paging.
The Server Driven Pagination field on the external data source
specifies whether to use client-driven or server-driven paging. If you enable
server-driven paging on an external data source, Salesforce ignores the requested page
sizes, including the default queryMore() batch size
of 500 rows. The pages returned by the external system determine the batches, but each
page can’t exceed 2,000 rows. However, the limits for the OData adapters for Salesforce
Connect still apply.
