Jun 03 2019 10:36 AM
Jun 03 2019 10:36 AM
I have a site in which I created two lists (Leave Approver Exceptions and Leave Requests). Each list uses a custom content type defined in our content type hub in SharePoint Online (the default "Item" content type has been removed). Both lists have/use PowerApps-customized forms.
I created a PnP Provisioning template from this site with the following command:
Get-PnPProvisioningTemplate -Out LeaveApproval.xml
I then created a new site and applied that template to it using this command:
Apply-PnPProvisioningTemplate -Path LeaveApproval.xml
The resulting site contains the two custom lists, but both still have the "Item" content type available and neither has the customized form. I didn't expect the custom forms to carry over, so that's not a big deal, but I did expect each list to have only the one defined content type. The custom views for each list are there, but one that was set up as a "Calendar" type view is now rendering as a standard (modern) list view (this is occurring in the original site as well, so it's not related to the provisioning process).
Also, it seems that the Quick Launch menu has a bunch of duplicates. Each of the custom lists appears twice, as does the Site Contents link.
Thinking this may be a glitch with using the .xml file type, I tried it again using:
Get-PnPProvisioningTemplate -Out LeaveApproval.pnp
The results (regarding the list content types and views) were the same, but this time, some entries in the Quick Launch (the lists and Site contents) actually got triplicated.
Is this expected/normal behavior of the PnP Provisioning process? If so, I can work around it or try another solution. Basically, what I want is a convenient way to add those two custom lists with their defined views (and customized PowerApps forms, if possible) to an existing site without wreaking havoc. The two lists serve as data sources for a PowerApp, so it's important that they be exact duplicates to minimize the work required to reconnect them to a new copy of the App.