Filter Issue=> Orchestrator HTTP Request "/odata/Robots"

Feedback Orchestrator
, , , ,
#1

Problem: I’m having an issue getting the filter by RobotEnvironments to work when executing an http request to pull in all the Robots within a specific Environment.

Sample Endpoint used:

"/odata/Robots?$filter=RobotEnvironments eq 'Environment1'"

Response:
{"message":"An error has occurred.","errorCode":0,"resourceIds":null}

— I have verified that the Environment string used is accurate on my end.

Workaround: I am using the .Where() method to filter the JArray by the ‘RobotEnvironments’ json key after the http request.

So, I can go with my workaround, but am curious as to what I’m doing wrong when trying to use the filter parameter in the endpoint. - It’s probably simple.

Your guidance is appreciated!

Thanks.

Clayton M

2 Likes
#5

Hello @ClaytonM!

It seems that you have trouble getting an answer to your question in the first 24 hours.
Let us give you a few hints and helpful links.

First, make sure you browsed through our Forum FAQ Beginner’s Guide. It will teach you what should be included in your topic.

You can check out some of our resources directly, see below:

  1. Always search first. It is the best way to quickly find your answer. Check out the image icon for that.
    Clicking the options button will let you set more specific topic search filters, i.e. only the ones with a solution.

  2. Topic that contains most common solutions with example project files can be found here.

  3. Read our official documentation where you can find a lot of information and instructions about each of our products:

  4. Watch the videos on our official YouTube channel for more visual tutorials.

  5. Meet us and our users on our Community Slack and ask your question there.

Hopefully this will let you easily find the solution/information you need. Once you have it, we would be happy if you could share your findings here and mark it as a solution. This will help other users find it in the future.

Thank you for helping us build our UiPath Community!

Cheers from your friendly
Forum_Staff

#6

Indeed, looks like a bug, especially because other fields work there.

1 Like