FolderId/OrganizationUnitId changes itself?

Help Orchestrator
, ,
1

So I have an application that triggers process through api “UiPath.Server.Configuration.OData.StartJobs”.

X-UIPATH-OrganizationUnitId is required in the header which is the folder Id of the released process.

For some reason the folder Id changes itself from 2500716 to 16230 today, which causes all the api calls to not work with error “Folder does not exist or the user does not have access to the folder”.

Any reason why the folder Id in orchestrator changes itself without any modification on my side?

2

I can’t speak to why the Folder ID change, perhaps due to an update to the Cloud Environment.

What I would suggest to protect yourself against changes in references to unique IDs that you don’t control, is instead of passing the header X-UIPATH-OrganizationUnitId to pass the X-UIPATH-FolderPath header, if the Folder is known upfront.

Alternatively if you don’t know the exact path of the folder (and this applies to other resources too e.g. Robots) is to request for the Folder Name/Path or ID using /odata/Folders first than pass the desired reference in future requests.

/odata/Folders?$filter=contains(DisplayName, 'New Folder')&$select=FullyQualifiedName

{
  "@odata.context": "https://cloud.uipath.com/****/****/orchestrator_/odata/$metadata#Folders(FullyQualifiedName)",
  "@odata.count": 1,
  "value": [
    {
      "FullyQualifiedName": "Shared/New Folder"
    }
  ]
}

https://docs.uipath.com/orchestrator/reference/building-api-requests

1 Like