SAP Knowledge Base Article - Public

2292164 - Duplicate records returned by an OData API Entity in SuccessFactors

Symptom

Duplicate records returned in two separate responses when querying an OData API Entity

For example, there is a sequence of OData API Entity calls using $top and $skip keywords in URL (similar to URLs mentioned below) and duplicate records are included in two separate responses

    https://apisalesdemo4.successfactors.com/odata/v2/User?$format=json&$select=userId&$top=200

    https://apisalesdemo4.successfactors.com/odata/v2/User?$format=json&$select=userId&$top=200&$skip=200

The same issue may occur when calling an OData API Entity via Boomi SF Connector

Environment

SuccessFactors BizX

Cause

Records might need to be ordered by 'order by' clause in OData query

Resolution

Provide 'orderby' keyword on field(s) with unique value in URL of the query for OData API entity, etc.:

    https://apisalesdemo4.successfactors.com/odata/v2/User?$format=json&$select=userId&$orderby=userId%20asc&$top=200

In case OData API entity call is made via Boomi SF Connector, set Sorts for a field(s) with unique value in operation of the connector, etc.:

KBAPicture.png

See Also

2272937 - How to identify which field to add in the 'orderBy' clause of the API query

Keywords

OData API, entity, duplicate, record, Boomi, SuccessFactors, connector, order by, sort, integration, web service, query, URL , KBA , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT , Integrations , Problem

Product

SAP SuccessFactors HCM Core 1511