pnp / powershell

PnP PowerShell
https://pnp.github.io/powershell
MIT License
672 stars 344 forks source link

[BUG] Issue with Document Sets Not Inheriting Properties on Communication Site via PnP PowerShell and XML Template #3586

Open J3D1m0 opened 10 months ago

J3D1m0 commented 10 months ago

Description:

When deploying Document Sets on a SharePoint Communication Site using PnP PowerShell along with an XML template, the Document Sets are not inheriting properties into the contained files as expected.

Steps to Reproduce:

Deploy a Document Set to a SharePoint Communication Site using PnP PowerShell. The XML template created by powershell before. After deployment, the Document Set does not inherit properties to its contained files.

Expected Behavior:

The Document Sets should inherit specified properties into the contained files, as is the standard functionality.

Actual Behavior:

The properties are not being inherited by the files within the Document Sets.

Environment:

PnP PowerShell Version: PnP.PowerShell 1.11.0 SharePoint Online Communication Site

EDIT: Tests in other tenants with other versions of pnp return the same result. Even if the inheritance is activated , the properties wont inherit to the files in the document sets.

diver7 commented 10 months ago

@J3D1m0 When you say " the Document Set does not inherit properties to its contained files." are referring to the metadata columns on the files? We just started seeing an issue a couple of weeks ago where we have a document set that is configured to share some columns with the files contained within it but they are not being populated on the files when uploaded. I think this is the same issue you are describing. Can you confirm?

We are using the Team Site base template and PnP Poweshell version 1.12.0 to create sites and apply a PnP site template. I have narrowed it down to it being caused by PnP Powershell applying a site template to a site. THat is the trigger that starts the issue. Not sure what PnP is doing during that application of the site template but something in there is breaking the Document Set content types Shared Columns functionality.

J3D1m0 commented 9 months ago

@diver7 yes i can confirm. we created round about 400 sites and deployt via pnp powershell the xml with the document sets and now the shared columns dont get the values from the set.

diver7 commented 9 months ago

@J3D1m0 Thanks for the confirmation. I created a new issue on the pnpframework repo because I saw some instructions that told me that issues with this pnp command should be there. Hopefully it will get some attention. Here is the link: https://github.com/pnp/pnpframework/issues/948