After installing template on other site collection why navigation messed up 2 times

Question

I have three quires on this please help :

I have sent site template details to xml file using commad : get-pnpsitetemplate -out filename.xml
and installed this in the other site collection, it worked well except little mess up in the navigation which appearing double times it seems. Please find attached screenshots of source & destiation site collection

why it came double in the navigation, what we need to avoid this? of Couse we can edit and remove. But expectation is not to come after installing the template.

1. Can u some insight like how we can use pnp contenttype, pnp app, pnp , pnpalert list how these we can use like pnp template , Kindly give me some example for these three.
2. Please let me know how to navigate to .xml file in C drive, I have tried to check in users folder but I have not found. However I could path for installing the template in the destination site rom powershell
3. So here we are installing the template of site from one site collection to another site collection in same tenant, this is clear for me.. Here my question is , Does it work if it is in different tenant? Please suggest
   if it works do we need to use same process? Please clarify
4. At a time can we connect only one site collection using pnponline command ?
5. can we save this template to CA that whenever we create a new site collection that time we can pick this template so it saves our time to use this template on top of site collection?

Answer 1

Hi @sns ,

I can also reproduce this on my end. When applying the site template to a site collection using Invoke-PnPSiteTemplate, the navigation links in source site will be added to the head while the links in the destination site will remain. As per my research, I'm afraid it is a default situation and you need to manage the navigation links manually after invoking the site template.

1. What do you want to achieve for content type/app/list with PnP PowerShell? You can search in this PnP.PowerShell directory to get the PnP commands you need.
   
2. The .xml file is stored in the location where you run the PnP command. For example, I ran the command under C:\WINDOWS\system32 so that the filename.xml was stored in C:\WINDOWS\system32. When I run the command like Invoke-PnPSiteTemplate -Path filename.xml, it will get the filename.xml from C:\WINDOWS\system32\filename.xml by default.
   
3. As per my test, it is not supported to invoke site template accross tenants. I got below error when running the PnP commands and I found some account infomation was stored in the .xml file.
   
4. When using Connect-PnPOnline to connect to a SharePoint Online site collection, we are connecting to only one site collection. I am a bit confused about this question you asked, could you please tell me more on this question?
5. SharePoint now offers several site templates that contain pre-populated pages, page templates, news post templates, and web parts that can be customized to fit the needs of your organization. Reference: Apply and customize SharePoint site templates. Also, you can create site templates to provide reusable lists, themes, layouts, pages, or custom actions so that your users can quickly build new SharePoint sites with the features they need. Learn more about how to create custom site templates for your organization.

   ---

If an Answer is helpful, please click "Accept Answer" and upvote it.
Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.