Hello All,
We are migrating from on-premise Orchestrator to cloud Orchestrator and discovering that the API functionality differs between the two deployments. In on-prem, we are able to use the OData filter to only find certain QueueItems created or processed during specified dates. However, those same filters on the StartProcessing property do not work in the cloud API.
Below, I’m showing two screenshots from Postman: one that shows we do have 7 queueitems in the returned data when not including the StartProcessing filter, and one screenshot that shows the error “Invalid OData query options.” The only difference is the addition of the StartProcessing filter.
How do we resolve this issue? I tried using $skip and $top, but those only make sense if the OData $orderby works reliably - and it doesn’t.
Is this date filter on QueueItems a known issue with Cloud API, and if so when can we expect a resolution? How do we get around it in the meanwhile?
Thanks for any assistance,
John
FYI, here are results coming back from the on-premise call: