SetItemReviewer API "BulkParameters must not be null"

Help Orchestrator
,
1

Hi all,

I’m trying to make an API call to update the reviewer on a queue item. My request body is:

 {
  "userId": 7,
  "queueItems": [
    {
      "RowVersion": "AAAAAAAA+j",
      "Id": 2084
    }
  ]
}

This matches what I’m seeing in the docs and on swagger. However when I call this I get an error I can find o information on whatsoever:

{
  "message": "setReviewerBulkParameters must not be null",
  "errorCode": 0,
  "traceId": "00-954df8f3023b22a8ac1d41007da1402d-dc9a4624eae6f0a2-00",
  "resourceIds": null
}

I could use some help figuring out what this means and getting my request working! Thanks

2

Hey

you will need to include the setReviewerBulkParameters parameter in your API request and set its value correctly

Regards!

3

What parameter is this? I cannot be it in the documentation.

4

hi @TJ_automates

Have you included header for X-UiPath-OrganizationUnitId??

image
image1542×560 22.7 KB

5

I have indeed

1 Like
6

Your JSON Body Structure looks ok
we can replicate the issue when running the call with an outdated RowVersion value
When using the actual RowVersion from the QueueItem and then perform the Rest Call, Reviewer is set successfully

7

I think you were right, it was a deleted item.

I have this working now with http requests, but I cannot get it to work using the orchestrator http activity. My payload is a valid json and the id/rowversions are correct, but the call alwas comes back with 400 - invalid odata query. I’m not using any filters so I’m stumped.

8

sorry, spoke too soon - not working in either method with the same error.

ResponseText : “{“message”:“Invalid OData query options.”,“errorCode”:999,“traceId”:“00-e05c0bca028df5878ccfe306a4995272-15149cff803c7204-00”,“resourceIds”:null}”

My request body/payload is {“userid”:18, “queueitems”: [{“RowVersion”:“AAAAAAAA/FU=”, “Id”:2229}]}

I’m authenticated with write permissions, and the unit id is passed into the regular http request.

My item is simply Failed, not deleted.

9

@TJ_automates

Hey. I have tried this on my swagger and that’s what I spotted.
The message setReviewerBulkParameters must not be null indicates that one of the parameters is either null or wrongly set.

In your case the id seems to be a bit odd. It may be due to the differences in organizations but the id is really short (2digits), while in my orgnanization all of the ids are at least 5 digits.
I have however such short ids for my AutomationHub users tho.

Could you please try calling /odata/Users to get the users and use one of the user ids with your call? Anyother user id than 18.
image

Also please make sure that you can set the reviewer manually on the item you’re using in the call.
If not, that may also be the reason why it’s not working.
image

10

Yeah, my rowversions are still short, but no doubt they’ll lengthen in no time! For what it’s worth I’m now just getting an invalid odata query response.

I have tried with a few users - I have 4 that I’m expecting the use this function and have tried with 3 of them!

Yes, I could set the reviewer for the last snippet I posted manually on orchestrator.

I can’t see to execute this on my own swagger, I can “try it out”, edit it and click execute, but nothing happens. Other calls seem to work fine.

11

@TJ_automates

It’s a weird situation if you ask me, it might be better to contact technical support in this case.

You can get your support id from Admin->Settings.

Hopefully they’ll be able to help you.

12

Tech support helped get me to the solution, which I’ll add here in case others come across this post -

The orchestrator http request activity needs to have the uipathodatasvc part REMOVED
The payload needs extra quotes around strings - each should be double quoted - so you’ll have a VB payload that looks like

“{”“userId”“:” + userID.tostring + “,”“queueItems”“:[{”“RowVersion”“:”“” + transactionRowVersion + “”“,”“Id”“:” + transactionID + “}]}”

and this passes through then as

{“userId”:7,“queueItems”:[{“RowVersion”:“AAAAAAABE08=”,“Id”:3089}]}

13

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.