- You're querying an API entity (directly via OData API or via Integration Center) which is a child of another MDF object and is configured with 'Effective dating: From parent' under 'Configure Object Definitions'
- You're using the fromDate and toDate parameters to filter the results based on their effective date
- The fromDate and toDate parameters have no effect on the results
- SAP SuccessFactors HXM Suite
- OData API
- Integration Center
In OData V2, for a composite child which is associated to an effective dated parent object, the fromDate, toDate, asOfDate in request will be ignored by default. To work around this, an additional parameter must be added to the query as explained in the resolution section.
If you're querying the entity directly via OData API:
Simply add a custom parameter to the request URL: filterParentDate=true.
Example: https://yourDCsAPIURL/odata/v2/PaymentInformationDetailV3?filter=externalCode eq 'XXXX'&filterParentDate=true
If you're using Integration Center to query the entity:
Currently, Integration Center does not support custom query parameters, so there's no way to achieve this behavior.
However, you may submit a request to include this feature as enhancement. Refer to 2090228 - How to Submit Ideas for SAP SuccessFactors Products
cannot, can't, not, working, able, successful, unsuccessful, unable, fails, failing, issue, message, returning, returns, problem, wrong, SF, successfactors, integration, Odata, api, request, call, query, get, payload, response, mdf, object, composite, association, child, effective-dated, from date, to date , KBA , LOD-SF-INT-MDF , Metadata Framework API (MDF) , LOD-SF-INT , Integrations , LOD-SF-INT-ODATA , OData API Framework , Problem