- Server based pagination provides performance boost when querying large data set using OData API.
- The issue of duplicates returned or missed records when querying the data can be avoided by using the "server based pagination".
"Image/data in this KBA is from SAP internal systems, sample data, or demo systems. Any resemblance to real data is purely coincidental."
- Successfactors HCM Suite
- OData API
- HCI / CPI - Cloud platform integration
In your "SuccessFactors Partner connector" > click in the "Enable Snapshot Pagination For OData Queries" flag.
Note: The customPageSize parameter is set to 200 only to show the example and usage of the parameter, this needs to be adopted by the implementation consultant accordingly based on the response time and number of navigation entities being queried.
In HCI / CPI
In your SuccessFactors connector, please use the pagination = Server Snapshot Based parameter.
Please check out this KBA 2830254 to review all the configs needed to enable correctly the server side pagination.
In Integration Center
In your Integration center interface > under "Destination Settings" tab, click in the "Enable Server Side Pagination".
We have one KBA for the same topic specific for CPI / HCI, kindly check this other KBA 2830254 - How to enable Server Snapshot Based in SuccessFactors OData API using SAP Cloud Platform Integration CPI
Duplicate records returned in successfactors query, slowness in odata api of successfactors, successfactors api performance, LOD-SF-INT-ODATA, how to use snapshot based pagination, duplicated values, missing records, data, inaccurate data, how to enable server based pagination, server side, Enable Snapshot Pagination For OData Queries , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-CUS , Boomi & CPI (HCI) Custom Content , LOD-SF-INT-HCI , Standard SF to 3rd Party CPI (HCI) Content , LOD-SF-INT-INC , Integration Center , How To