Tridion Stack Exchange is a question and answer site for Tridion developers and administrators. It only takes a minute to sign up.
Sign up to join this community
We are always facing an issue with mis-matched uuid, for few Schemas in our SDL Web 8.5 CMS.
For every deploy we have to manually update the Schema uuid to the value for the current environment. This needs to be done for every deploy. Is it possible to fix this once and far all? We should not face this issue while content port, the uuid should be environment specific.
Is there anything we are missing here?
In general, (XML) Schemas have a so-called Namespace URI which also affects the Components based on the Schema.
In Tridion, this Namespace URI is a property of a Schema. You cannot edit it directly, but it is obtained from the XSD. The default Namespace URI for newly created Schemas is a UUID (to ensure it is distinct from any other Schema).
The reason for this introduction: if you port a Schema between environments, its Namespace URI does not change. This is fortunately so, because changing the Namespace URI of a Schema on which Components are based has potentially huge impact; it effectively invalidates all existing Components based on the Schema.
I guess you are first manually creating the new Schema in both environments (effectively resulting in Schemas with different Namespace URIs) and later porting the Schema changes, resulting in the Namespace URI getting in sync between the environments (but a one time change on the target env.) ?
I'm surprised that you're having a problem with these, as it's not normally a problem having different Schema UUIDs between environments.
As long as the Schema names and root element are the same, then you should be able to Content Port Components (and other Schemas) between environments without issue.
Do you just want to keep the UUIDs the same for cleanliness or are you experiencing a different problem if they're not consistent between environments?
