You’re offline. This is a read only version of the page.
177
Hi, I have sitemap changes that are being published into several environments. The sitemap publishes fine in some of the environments, but when it publishes in another tenant, the sitemap changes do not take (Azure pipeline). All other changes from the solution appear in that other tenant. Is there a bug with the sitemap across tenants?
Hi there!
The issue might be caused by the fact that your sitemap exists in multiple solutions (layers) and may have an Active layer on top.
An active layer for the sitemap component represents changes done directly in the UI. Since those changes need to be stored in a solution, a special solution is created, called "Active". This will be the topmost solution and changes made directly in the UI will take precedence over changes coming from other solutions. This can become complex due to the fact that XML components, such as sitemaps merge all layers and what the user sees can be something other than expected.
Please have a look at the official documentation regarding solution layers here:
docs.microsoft.com/.../solution-layers
And here you can understand more about how sitemaps are managed and how their definition is merged, in order to get the actual definition you see in the UI: docs.microsoft.com/.../understand-managed-solutions-merged
If there is an active layer for the sitemap, you should be able to remove it by selecting the component and then choosing Solution Layers.
Hope this helps.
Share
Report
All responses (
Answers (
