I’m getting the following error trying to publish an updated version of a project. I haven’t changed any settings and indeed cannot find this setting in the project file. How can I resolve this?
Error: Publish of Process project to Orchestrator failed. Project type has changed since the latest published version (was Process, now is BusinessProcess). Revert the project type or publish a new project.
@TJ_automates Have you referred this Post
Unfortunately that post is of no help - I am not changing the project name and the existing process is not inactive.
Deactivating the existing process has not helped either - I still cannot publish
Faced error while trying to publish a process to Orchestrator "Project type has changed since the latest published version (was Undefined, now is Process). Revert the project type or publish a new project "
Possible cause of the issue: ProjectType value from the [dbo].[PackageMetadata] table is causing the problem. When you publish any project from the 2018.4 version of the UiPath Studio, it gets published with ProjectType as 0 which means Undefined.
As a permanent fix, you should make sure that the robots and Orchestrator are on the same version. Hence, please consider upgrading the robot to match the version of the Orchestrator.
For the failed packages with the error “Project type has changed since the latest published version (was Undefined, now is Process). Revert the project type or publish a new project.” you can check these approaches:
Approach #1 the easiest way is by opening the failed process in UiPath Studio → renaming the project and publishing it to your Orchestrator tenant
A not elegant way to achieve the same is by downloading and installing the NuGet Package Explorer from the Microsoft Apps
- Access the On-Premise Orchestrator → Tenant → Packages → find the not migrated package process → Version → Download package
- Open the downloaded nupkg file with NuGet Package Explorer and access Edit Metadata Source
- Modify the value for and . Make sure that Title and Id have the same value and it is unique in your Orchestrator. Then Save the changes.
- Save the whole changes from File → Save As → Save.
Access the On-Premise Orchestrator → Tenant → Packages → Upload → Browse the .nupkg file → Upload it
You can add the process to your desired folder
Approach #2: Access your Orchestrator database server
Update the ProjectType value to 0 for the impacted processes in the [dbo].[PackageMetadata] table
Example (adapt it based on your package Identifier and versions as you have in the [dbo].PackageMetadata] table):
WHERE [Identifier] = 'YOUR_PROCESS_NAME' AND ([Version] = '1.0.9' OR [Version] = '1.0.7')