Symptom
- In OData API v2 (/odata/v2/), applying $filter to properties of expanded navigation entities has no effect.
- Queries that use $expand with a nested path (for example, eventNav/picklistLabels) return all related records instead of the filtered subset.
- Results include all locales rather than only the specified locale (for example, en_US).
Environment
- SAP SuccessFactors HCM Suite.
- OData API.
- OData API Framework.
Reproducing the Issue
- Query SFOData.EmpJob with $expand=eventNav/picklistLabels.
- Add $filter=eventNav/picklistLabels/locale eq 'en_US'.
- Observe that the response contains picklistLabels for all locales, not only en_US.
Cause
In OData v2, $filter is applied only at the root entity level and is not evaluated on expanded navigation entities.
Resolution
- This is a product limitation of OData v2: filtering on expanded navigation entities is not supported.
- OData v4 supports filtering on $expand, but it is currently not available for the SuccessFactors OData API.
- There is no server-side filter support for expanded entities in OData v
Keywords
nested query, child entity, server-side filtering, response payload, query parameters, design constraint, expected outcome, language code, result set, subresource, deep query, API design, request example, data retrieval, data selection , KBA , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , Problem
Product
SAP SuccessFactors HCM Core all versions
SAP Knowledge Base Article - Public