Migration: package.xml refer to content's parent by key instead of id
To sync a lot of things between Umbraco instances, we use uSync and that works great. Content is only synced on the development machines, but any other environment (test, acc and prod) does not sync content. We don't use Cloud, so no Deploy ;)
So when we have content that is required for the site te function, I create an automatic migration with a package.xml of the content that is required. In this case a node that contains information for the site header (like the logo, menu items etc). I removed the individual fields for this example:
The problem is that this header node is located in a certain spot in the content tree. In the package.xml this is apparent: parentID="1076" and
path="-1,1073,1076,1094"
However....the id's between the environments are for all the nodes are not always the same. So parentID 1076 does not exist in all environments, which will place the new header node on the root level of the site.
It there a way to match the parent by key? Or how would you guys solve this? Create the content programmatically?
Migration: package.xml refer to content's parent by key instead of id
To sync a lot of things between Umbraco instances, we use uSync and that works great. Content is only synced on the development machines, but any other environment (test, acc and prod) does not sync content. We don't use Cloud, so no Deploy ;)
So when we have content that is required for the site te function, I create an automatic migration with a package.xml of the content that is required. In this case a node that contains information for the site header (like the logo, menu items etc). I removed the individual fields for this example:
The problem is that this header node is located in a certain spot in the content tree. In the package.xml this is apparent: parentID="1076" and path="-1,1073,1076,1094"
However....the id's between the environments are for all the nodes are not always the same. So parentID 1076 does not exist in all environments, which will place the new header node on the root level of the site.
It there a way to match the parent by key? Or how would you guys solve this? Create the content programmatically?
is working on a reply...