Skip to content

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

@kachihro

Description

@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

Metadata

Metadata

Assignees

No one assigned

    Labels

    bugSomething isn't working

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions