Having an odd issue with the Cloud Orchestrator Swagger interface (v17 according to the web page). This is an enterprise license cloud instance not community.
After setting up Authentication, using the /odata/QueueItems swagger GET call using the default Paramters settings, the call works just fine returning a 200 with a resulting Response Body of all queue items found.
But, changing the $orderby parameters to include CreationTime, it returns a HTTP 400 with this error:
Interestingly, clearing CreationTime from $orderby and putting CreationTime in $select, it works just fine again. It returns with a HTTP 200 with a list of the queue items found each its respective CreationTime attribute only like it should.
This /odata/QueueItems API works in an v2022.10 onpremise Orchestrator just fine using $sortby with CreationTime just fine.
Thanks for both replies. While the replies are interesting, looking to find out why its not working as stated. Not for alternatives at this point. The API in question is currently used within a custom built application against an onpremise Orchestrator v2022.10.4 (I think) and it works just fine using $orderby = CreationTime.
I just tried it with my personal community licensed Cloud Orchestrator tenant in Swagger. In that tenant’s swagger interface the /odata/GetItems GET API works like it should using $orderby = CreationTime.
For some reason in this enterprise license Cloud Orchestrator tenant’s swagger interface, that API call using $orderby = CreationTime fails with a HTTP 400. Using CreationTime in the $select parameter it returns a HTTP 200 - not sure if this test is helpful but clearly shows the CreationTime attribute is functional in other input parameters to that API call.
