After 1H 2021 release, you are observing duplicated records in the response even when you are correctly using the "Server Side Pagination" mechanism in Integration center or OData API queries.
This is happening for the OData Employee Central API queries like PerPerson entity.
- SAP SuccessFactors HXM Suite
- OData API
- Integration center
If using snapshot pagination and the $orderby properties are not present in the in $select part of the query, in backend, the system will generate incorrect SQL, which leads snapshot pagination doesn't work. Then the query will fall back to normal query without snapshot pagination suffering of duplicate and missing records in the response.
The issue was identified and it will be fixed with patch planned for b2105p8 (9-Jun-21: preview, 11-Jun: production).
Internal references number PTCH-36133 and API-19905.
While the patch is not delivered, please evaluate the following:
Workaround till patch deployment:
If you are observing duplicated records inside your integrations even with "Enable server pagination" checkbox under "Destination settings" enabled, please remove the fields from your selections of "Advance Sorting" under "filter and sort" tab.
OData EC API:
If your OData API is using $paging=snapshot and it has $orderby with fields that are not present in the $select too, please remove your $orderby or order only for the business key fields like personIdExternal for PerPerson entity.
duplicated records, missing records, pagination, server side pagination 1H 2021 error, integration center, Odata, Employee Central OData API, issue , KBA , LOD-SF-INT-EC , Employee Central SFAPI & OData Entities , LOD-SF-INT , Integrations , LOD-SF-INT-INC , Integration Center , LOD-SF-INT-ODATA , OData API Framework , Known Error