Symptom
- An issue was encountered when implementing a custom OData filter for non-null values in SAP SuccessFactors, e.g.: cust_MDFObject?$select=externalCode,cust_1,cust_2,createdDateTime&$filter=(cust_1 ne null and cust_2 ne 'null' and createdDateTime ge '2000-01-01')
- Despite the filter being set to exclude null values, null records are still being returned from SAP SuccessFactors API.
Environment
Metadata Framework API (MDF)
Reproducing the Issue
- Implement a custom OData filter in SAP SuccessFactors to exclude null values.
- Execute the query and observe the returned records.
Cause
- The issue arises due to the complexity of the business cases involved.
- The current analysis does not provide a quick fix for the issue.
Resolution
- As a workaround, use the 'contained in' filter until the issue is resolved, e.g.: cust_MDFObject?$select=createdDateTime,cust_1,cust_2,effectiveStartDate,externalCode&$filter=(cust_1 in ('B','T') and cust_2 ne null and createdDateTime ge '2000-01-01')
- Our Engineering team are working on a permanent fix for this (no ETA on this due to its complexity, our internal reference is MDF-88509).
See Also
Refer to KBA 3025683 - How to filter records which have a blank field in a query - SAP SuccessFactors OData API.
Keywords
SAP SuccessFactors, OData API, null values, filter, CPI, MDF, custom filter, records, query, 3025683, MDF object, API, SuccessFactors, SF, SFSF, custom, filter, "contained in", is contained in , KBA , LOD-SF-INT-MDF , Metadata Framework API (MDF) , Known Error
Product
SAP SuccessFactors Platform all versions