API orderby limitations

(0) Share

Report

Posted on by Derek Ip

Hello,

I'm trying to query a decimal field and have it order by highest to lowest, I add the orderby=MY_FIELD desc and it works for pretty much every field except for one, it will give me results but won't order by it (desc or asc).

The field is a decimal calculated field but I've done an orderby on another calculated field in the same entity and have no issues.

Anyone have ideas?

Thanks!-

Categories:

Customization / Solutions / SDK and API

All responses (3)

Answers (0)

LeoAlt 16,331 Moderator on at

Like (0)

Report

RE: API orderby limitations

Hi Derek,

I created same project entity like yours and same calculated field remaining_hours, with your query filter:

?$select=new_remaining_hours,new_name,statecode&$filter=statecode eq 0&$orderby=new_remaining_hours desc

However, the calculated field works without issue.

While my testing is by executing web api in browser address bar and console directly, so there is no other code with it.

Could you try to create a new field to get substracted value from estimated hours and delivered hours to test whether the issue still exists?

If the issue still exists, could you share me:

> some of your other code in your JS library

> or any customization such as other JS libraries or business rule or workflow on your project form

> and your CRM version? (Mine is 9.1.0.8226 online.)

Just want to confirm whether there is any of possible factor that may has impact on your final result.

Regards,

Leo
Derek Ip 15 on at

Like (0)

Report

RE: API orderby limitations

Hi Thank you for the response.

here's my field.

This is my query "ovx_projects?$select=ovx_remaining_hours,ovx_name,statecode&$filter=statecode eq 0&$orderby=ovx_remaining_hours desc"

this is my first 5 returns.

It doesn't seem to matter if I do desc or asc the order is the same with this return, it's not sorting by ovx_remaining_hours. I've tried doing the same to another calculated field I have and I can order it based on the number of that field.

Thank you
LeoAlt 16,331 Moderator on at

Like (0)

Report

RE: API orderby limitations

Hi Derek,

I created a calculated decimal number field to calculate twice of the revenue field for account entity and did not encounter your issue.

My full criteria is below:

$select=name,revenue,new_doublerevenue&$orderby=new_doublerevenue desc&$filter=new_doublerevenue ne null

Field properties:

Operation:

Could you share me more details such as original fields for calculated fields and the calculated fields properties of yours?

Regards,

Leo