updateUserRole not recognising inputs

NateBI
NateBI Contributor
edited April 2 in Workflows

Hi Folks,

Issue:
I'm getting the error:
status 400 reading NebulaClient#executeServiceToService(UUID,String,String,Boolean,ExecutePackageVersionFunction); content: {"status":400,"statusReason":"Bad Request","message":"The following input values are invalid: [Invalid type: expected PERSON. (Could not find user in system. Does it exist and do you have proper permission?)]","toe":"AKE4K5T2I5-AHC2P-1QSCF"} : com.domo.bedrock.jaxrs.client.exception.BadRequestException

Context:

Using the updateUserRole Function from the Domo Users package. I'm passing in a PERSON and a text input "Admin". Any thoughts as to why this happening?

Already tried:

+ Editing the User's role manually and it works so I have permission

+ Shared a dataset with the User and it works so the user exists in the system

Side Note
On a seperate but similarly weird note I was also getting an error saying "couldn't find user_id" which was an input param in the start tile that I had created but removed and was no longer being reference. Is this to do with some type of cache issue? (I've recreated the parameter to by-pass the error for now and haven't removed to test yet - trying to avoud an endless deploy create new version loop)

All help appreciated

Tagged:

Best Answer

  • JosephMeyers
    JosephMeyers Domo Employee
    Answer ✓

    Hey NateBI I got your ticket and figured out what the issue is. I've sent a response back to the Support team but am posting here so other know what is happening. Unfortunately, we have a bug where editing a start parameter is only saving changes to the displayName and this causes a missmatch between the display and what the backend is using. Normally this causes the Start to immediately fail but in some of your earlier versions you had another param with that same name and then it would get past the start and fail on the function because the values weren't being set correctly. We are working on an immediate hotfix for the issue but for you or anyone else seeing this the quick workaround is to just delete and remake the start parameters.

Answers

  • GrantSmith
    GrantSmith Coach

    Are you passing in the User ID (not the user name or email but the Domo internal user id) for the user's role you want to update?

    **Was this post helpful? Click Agree or Like below**
    **Did this solve your problem? Accept it as a solution!**
  • JosephMeyers
    JosephMeyers Domo Employee

    Can you go to the function in Code Engine and click the arrow to test run it there? See if that works or provide the error information if it doesn't. Or you could also try again and get a fresh TOE on that error and I can take a look and see if that shows anything.

    Screenshot 2025-04-11 at 3.35.39 PM.png

    From what you've explained it seems like you are doing things correctly. It would help to see your workflow executions and follow things through. It may also be easier to escalate to support and have a ticket to come over to my team and we can take a closer look. Same with the side note issue. That one looks like you are referencing the variable somewhere still but we'd need to look at the workflow itself.

  • NateBI
    NateBI Contributor
    edited April 15

    @GrantSmith Yep using the PERSON type, so when validating manually it's a dropdown entry (this converts to user_id behind the scenes I believe)

    @JosephMeyers the function runs successfully in code engine, but still not in the workflow. I'ved created a same named ticket now. Also see user_id (the side note error) error below:

    image.png
  • JosephMeyers
    JosephMeyers Domo Employee
    Answer ✓

    Hey NateBI I got your ticket and figured out what the issue is. I've sent a response back to the Support team but am posting here so other know what is happening. Unfortunately, we have a bug where editing a start parameter is only saving changes to the displayName and this causes a missmatch between the display and what the backend is using. Normally this causes the Start to immediately fail but in some of your earlier versions you had another param with that same name and then it would get past the start and fail on the function because the values weren't being set correctly. We are working on an immediate hotfix for the issue but for you or anyone else seeing this the quick workaround is to just delete and remake the start parameters.

  • JosephMeyers
    JosephMeyers Domo Employee

    The hotfix has been released and your workflows should behave as expected again.

Categories