Currently sorting in OData API's works only at Parent API level, when we try to sort the result data set using a field from navigation it does not support.
Note: This is a known limitation in Successfactors OData API.
Successfactors OData API
Reproducing the Issue
- Choose any object definiton in configure object definiton, To this object you have associated another object in one to many relation (1:N relation)
- Now,under manage data create some data for this object
- For this example, we have chosen cost center as the base entity and navigate to LegalEntity
Currently this is a limitation in the OData API.
No work-around exists for the situation.
Sorting , orderby, orderby in successfactors , odata api support for orderby , LOD-SF-INT-ODATA , LOD-SF-INT-EC , can you sort navigations in odata , odata api support for orderby , navigations in successfactors odata cannot be sorted , successfactors odata api , KBA , limitation of orderby in successfactors , LOD-SF-INT-ODATA , OData API Framework , LOD-SF-INT , Integrations , LOD-SF-INT-CUS , Boomi & CPI (HCI) Custom Content , Problem