We are deploying Employee Service Center in our environment. When building the Taxonomy (mega menu) structure in lower environments, I was continually prompted to move to the Employee experience taxonomy application scope (the OOB application scope) as I built out the topic structure (topics, child topics, etc.) and moved the catalog items under the proper topic. However, many of the catalog items were built in a different scope, such as the "global" scope or a custom application scope.
Now, when trying to promote the Employee experience taxonomy application scope, I am getting many cross-scope preview problems (like the one below) and my only option is to "Skip Remote Update."
Has anyone else encountered this? If yes, how did you handle? What is best practice when initially building your taxonomy for ESC and trying to capture the taxonomy topic changes for catalog items? It seems very cumbersome to make the changes in each individual application scope, especially when making dozens of taxonomy changes.
Example of cross scope preview problem:
"Cannot commit Update Set 'EC_Taxonomy_20241210_DT_Phase2' because: Update scope id '7f5dabf71b7df1908decc9da234bcb08' is different than update set scope id '9f678ed6c3003010069aec4b7d40ddba'. Resolve the problem before committing."
I appreciate any guidance on how best to handle this situation.
