"PerRobot" Type Asset Create error

Help Orchestrator
, , , , , , , ,
1

image

image
image897×258 19.7 KB

When I request an API like this, I get an error like “{
“message”: “A valid classic folder id is required for this operation”,
“errorCode”: 1009,
“traceId”: “00-158f0f5bad2c7357d335a32979d5cc24-1ea744c5dc218a2c-00”,
“resourceIds”: null
}” Tell me how to fix it. Automation suit version is 2022.10 version. Folder management is modern
Management cannot be changed to a classic folder.

2

Hi @sgkim

Try following these steps. It might help you.

  1. Check API Documentation: Review the API documentation for the specific API you’re using. It’s possible that there might be alternative parameters or endpoints that you need to use when working with modern folder management.
  2. Contact UiPath Support: Reach out to UiPath’s support or community forums. They might have insights or workarounds for your specific situation, especially if you’re encountering issues due to the modern folder management setup.
  3. Version Updates: Sometimes, newer versions of software might address specific issues or limitations. Check if there are any updates or patches available for your version of UiPath that might resolve this problem.
  4. Alternative Approaches: If your API request involves actions that are not compatible with modern folder management, consider alternative approaches to achieve your desired outcome within the constraints of modern folder management.

Check out this thread. This might help you.

Regards

3

It can be created in a global type, but if the type is “PerRobot”, “{
“message”: “A valid classic folder id is required for this operation”,
“errorCode”: 1009,
“traceId”: “00-4d9f78a9f99f8465a9decf94ef7841fa-e44eb7e8603c6e2d-00”,
“resourceIds”: null
}” This error keeps responding.

4

@sgkim

As in modern we do not have robots I believe it is failing…you need to use PerUser and use User values in modern

image
image1011×638 35.4 KB

Even in assets if you see now…it would ask for user in modern

cheers

5

Can you give me an example by any chance?

Thank you in advance

6

@sgkim

This is what is to be added to request now

"UserValues": [
    {
      "UserId": 0,
      "UserName": "string",
      "MachineId": 0,
      "MachineName": "string",
      "ValueType": "Credential",
      "CredentialUsername": "string",
      "CredentialPassword": "string",
      }
  ]

and use ValueScope to be PerUser

cheers

7 
{
    "Name": "PerUserTEST",
    "ValueScope": "PerRobot",
    "ValueType": "Credential",
    "UserValues": [
        {
            "UserId": 120,
            "UserName": "test",
            "MachineId": null,
            "MachineName": null,
            "ValueType": "Credential",
            "CredentialUsername": "test1234",
            "CredentialPassword": "1234"
        }
    ]
}

If ValueScope is set to “PerUser”, the error is answered. But if you use “PerRobot”, it works fine

Thank you.

8

@sgkim

So I hope setting this and using uservalues is working now?

Or do you have more issues?

cheers

9

It’s working very well

1 Like
10

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