How to export a UiPath Automation Project from UiPath Orchestrator
Blueprint can import UiPath projects that are within exported .nupkg files created by UiPath Orchestrator. This describes this process.
Publishing your Automation to Orchestrator
If the option is available, select Include Sources as well (Found under Compilation Settings)
To Create a .zip file that contains a UiPath Automation Project
- Log into UiPath Orchestrator and navigate to your tenant (top-left)
- Select 'Packages' to list your UiPath packages
- For the package you'd like to export select the three dots at far-right, then select "View Versions"
- For the version you'd like to export select the three dots on the right side, then select "Download Package"
- Save the .nupkg file to the location of your choice
(Optional) .nupkg files can be imported directly into Blueprint; however, Blueprint has an import size limit of 300 MBs for individual files. If you find your file exceeding this limit, only the net45 folder is necessary. To extract only that folder, follow these steps:
- In Windows file explorer, change the extension of the file to ".zip" then unzip the file
- Navigate within the unzipped file to the contents of /lib/net45 folder
- Zip the contents of this folder. It is this zip file that you'll be able to import into Blueprint
How to get Custom Dependencies of a UiPath Automation Project
When exporting a package from Orchestrator, custom dependencies or libraries will not be included in the downloadable .nupkg file. To include these items:
- Log into UiPath Orchestrator and navigate to your tenant (top-left)
- Select 'Libraries' to list your UiPath libraries
- For the library you'd like to export select the three dots at far-right
- For the version you'd like to export select the three dots on the right side, then select "Download Library"
- Save the .nupkg file to the location of your choice
- In Windows file explorer, change the extension of the file to ".zip" then unzip the file
- Navigate to the zip of the package that references the dependencies
- Create a folder to keep all called dependencies
- Copy and paste the unzipped dependency files in this folder
- Zip the contents of this folder. It is this zip file that you'll be able to import into Blueprint