topic Re: odata v2 sorting not working (Java v1 backend service) in Application Development and Automation Discussions

odata v2 sorting not working (Java v1 backend service)

WFlats — Thu, 15 Jul 2021 08:25:57 GMT

I want to find the earliest start of a task entity at a certain location with an odata v2 read operation.
This is the code

oModel.read("/Tasks", {
filters: [new Filter("location_ID", FilterOperator.EQ, sLocationID)],
sorter: [new Sorter("actualStart", false)],
urlParameters: {
$top: 100 // revisit
},
success: function (oData) {...

I usually only have to use "$top: 1" as this first entity contains the earliest task.

But I realised that the data is not sorted.

When I look at the HTTP request then the payload doesn't contain any "orderBy" statement.

SAP support told me to ask a question here as it is custom code.

Can anyone see an error in my code? I used such read operations with a sorter many times and can't see a mistake.

Re: odata v2 sorting not working (Java v1 backend service)

subhajit — Thu, 15 Jul 2021 15:27:45 GMT

Hello,

Replace the parameter name with ‘sorters’ instead of ‘sorter’..

Also make sure your alias points to the correct class..

Re: odata v2 sorting not working (Java v1 backend service)

WFlats — Thu, 15 Jul 2021 15:43:54 GMT

Subhajit provided the corect answer in his comment. Thanks very much!

Not sure how many times I checked the code but couldn't see it...