SAP Knowledge Base Article - Preview

2920680 - OData API: Filtering records by a 'lastModifiedDateTime' range (combining 'lt' or 'le' and 'gt' or 'ge') yields an unexpected result

Symptom

You're querying a specific user's effective dated entity (such as EmpJob) to get records that were modified between two datetimes, similar to the one below:

  • https://XXXX/odata/v2/EmpJob?$filter=lastModifiedDateTime gt datetimeoffset'2020-04-21T07:38:00Z' and lastModifiedDateTime lt datetimeoffset'2020-04-21T08:38:00Z' and userId eq '11111111'

You know by checking the user profile's Job Information history that no modifications were done within the provided time range, and therefore the query's response should be empy. However, a record is returned with lastModifiedDateTime outside the specified range.


Read more...

Environment

  • SAP SuccessFactors HXM Suite

    • OData API

    • Integration center

Product

SAP SuccessFactors HCM Suite all versions

Keywords

gt, ge, le, lt, greater than, lesser than, greater or equal to, lesser or equal to, datetime, last modified date, lastmodifieddate, time-based, effective-dated, not working, wrong results , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , Problem

About this page

This is a preview of a SAP Knowledge Base Article. Click more to access the full version on SAP for Me (Login required).

Search for additional results

Visit SAP Support Portal's SAP Notes and KBA Search.