[BUG] Reset-PnPDocumentId doesn't work for DOC-SETS

[kachihro]

Notice

Many bugs reported are actually related to the PnP Framework which is used behind the scenes. Consider carefully where to report an issue:

1. We are migrating files to new sites, and want to re-generate DocIds.
2. This command works for DOCUMENTS - using the new setting for the destination site
3. BUT - this doesn't appear to work for Doc-Sets themselves (aka- superFolders)
4. Have tried with the specific URL for the DocSet - and also using the Content Type approach - neither works

Reporting an Issue or Missing Feature

Reset-PnPDocumentId -File /sites/dest/library/File.Docx ✅
Reset-PnPDocumentId -File /sites/dest/library/DocSet ❌

Reset-PnPDocumentId -Library $libraryName -ContentType (Get-PnPContentType -List $libraryName | Where-Object Name -eq 'DocSetCT') ❌

Expected behavior

Newly generated DocumentId - for the Document Set

Actual behavior

No change - old DocumentId remains in place

Steps to reproduce behavior

Reset-PnPDocumentId -File /sites/dest/library/File.Docx ✅
Reset-PnPDocumentId -File /sites/dest/library/DocSet ❌

Reset-PnPDocumentId -Library $libraryName -ContentType (Get-PnPContentType -List $libraryName | Where-Object Name -eq 'DocSetCT') ❌

What is the version of the Cmdlet module you are running?

3.1.0 (thanks for all the updates !)

Which operating system/environment are you running PnP PowerShell on?

• [ X ] Windows
• Linux
• MacOS
• Azure Cloud Shell
• Azure Functions
• Other : please specify

[gautamdsheth]

hey @kachihro , if the document ID remains the same, then the one that was assigned is the correct one and it wont be changed. Moving this to discussion since it is not an issue with the cmdlet itself but is more a tenant specific issue . Check the docs :

https://pnp.github.io/powershell/cmdlets/Reset-PnPDocumentId.html

[kachihro]

Thanks - and yes, I agree.

My issue was for some documents that were moved into the site - and we wanted to 'regenerate' according to the new site Document-Prefix. This works almost perfectly !

BUT - it doesn't work for Document Sets. It only works for Documents.

That's the issue/bug that I've raised here. It's not a discussion - this doesn't work for document sets.