When attempting to run a simple HTTP request to the orchestrator, the OData count is missing when I run remotely (started from assistant). When running directly from studio this count is present, I have saved both responses:
Ran remotely:
I don’t think its due to the folder path as, when I run it on my local studio, the process works perfectly fine. It’s as soon as I publish it that the HTTP request returns slightly different responses.
Here’s my request:
String.Format(
"/odata/QueueItems?$filter=QueueDefinitionId eq {0} and CreationTime gt {1} and CreationTime lt {2}",
In_dicQueueNameToQueueID(Queue),
In_arr_dtmReportDateRange(0).ToString("yyyy-MM-ddTHH:mm:ssZ"),
In_arr_dtmReportDateRange(1).ToString("yyyy-MM-ddTHH:mm:ssZ")
)
In a previous step I loop through each queue in a folder and store its name and ID in that dictionary
You are passing a queue definition id here right, just pass that folder path in which the queue is present in the Orchestrator HTTP activity which will do the trick, Try once please…
Do you mean in the Misc input “Folder Path”? If so that value is populated.
I am still receiving a valid JSON response from this request it’s only the odata count that is missing
Yes it does have the items, I need to keep track of the number of returned items as its the escape condition in my while loop. As I’m querying a cloud based orchestrator it only returns 1000 items, so having this OData count helps me keep track of how many loops are needed to extract all items.