Closed bjarnef closed 9 months ago
Yes, I can see why that would come about. What's happening is:
I had a element type named "Block Education Progress" which I renamed to "Education Progress"
So now in your local environment you have a single document type with alias educationProgress
and a GUID key.
The same document type exists upstream with the alias blockEducationProcess
and the same GUID key.
and created a new element type with name "Block Education Progress".
And now another document type with a different GUID key and the alias blockEducationProcess
On deployment, the first document type can be updated. But as it's all done in a transaction, the second has a problem. It's finding an existing document type with the same alias but a different GUID key, and throws an error on that (as you can't have two document types with the same alias).
I think you can resolve if you deploy this in two parts - first the rename of the existing document type, and then the addition of the new one. That should serve as a workaround to allow you to deploy what you need.
Will consider though if we can ignore this check in the state you have - as the case here is that there won't be a problem once the full deployment is completed, as the clashing item will have been renamed to have a new alias.
It seems Deploy was a bit confused, when the remote environment also have the original entity with alias blockEducationProgress
.
It seems it was better to rename to something temporary first like blockEducationPro
.. and then update afterwards when the orignal block blockEducationProgress
was renamed to educationProgress
.
@AndyButland yes, I think I have come across this issue before, but I have solved it now.
If renaming alias to something which already exists, it seems it is best to rename to something temporary first, so the original as new entities don't clash with each other.
On an Umbraco Project I had a element type named "Block Education Progress" which I renamed to "Education Progress" and created a new element type with name "Block Education Progress".
Now after transfer to remove environment and extraction schema files, I get the following error.
Umbraco v12.3.1 Deploy v12.0.4