SAP Knowledge Base Article - Preview

2920680 - Using lastModifiedDateTime Range Filtering - SuccessFactors OData API

Symptom

When querying an effective-dated entity (such as EmpJob or EmpCompensation) using the OData API with a filter on lastModifiedDateTime to retrieve records modified within a specific datetime range, you might receive a record that was not modified within that range.

For example, if you aim to retrieve only records modified in 2024, you might use:

  • $filter=(lastModifiedDateTime gt (greater than) datetimeoffset'2024-01-01T00:00:00Z' AND lastModifiedDateTime lt (less than) datetimeoffset'2025-01-01T00:00:00Z')

Even though you verified that no modifications occurred within the specified time range, the query returns a record with a lastModifiedDateTime outside the range. 

NOTE: The same behaviour happen in Integration Center, as it is based on OData API resources.


Read more...

Environment

SAP SuccessFactors HXM Suite

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 , How To

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.