I have a similar quick launch navigation structure as in the picture below:
The Templates node points to a document library. It's url is {site}/Templates/Forms/AllItems.aspx.
Because I'm using the pnp provisioning engine to add and update artefacts in SharePoint Online, I have a provisioning template which adds or updates the Templates list.
As soon as I apply this provisioning template, my Templates navigation node will disappear.
Is there any reason why updating a list will remove the navigation node pointing to it? Is there any way to prevent that from happening? Imagine having 15 navigation nodes grouped under a navigation header all with audience targeting. These nodes will disappear as soon as I apply an update to the site and it will be time consuming to built everything back up since audience targeting is not supported in the schema.
Does anybody have a solution for this. I am also facing this issue sometimes but not every time using PnP PowerShell 1.12.0. Thank you in advance for any suggestions to fix this.
I have a similar quick launch navigation structure as in the picture below:![image](https://user-images.githubusercontent.com/14358537/210634466-1d360e7c-17ab-4e5f-a17f-492896fa6596.png)
The Templates node points to a document library. It's url is {site}/Templates/Forms/AllItems.aspx.
Because I'm using the pnp provisioning engine to add and update artefacts in SharePoint Online, I have a provisioning template which adds or updates the Templates list.
As soon as I apply this provisioning template, my Templates navigation node will disappear.
Is there any reason why updating a list will remove the navigation node pointing to it? Is there any way to prevent that from happening? Imagine having 15 navigation nodes grouped under a navigation header all with audience targeting. These nodes will disappear as soon as I apply an update to the site and it will be time consuming to built everything back up since audience targeting is not supported in the schema.