Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[BUG] Get-PnPClientSidePage cmdlet always throw 'does not exist' error in some tenants' root site collection #3666

Closed
1 task
RogerZhang-CatapultSystems opened this issue Jan 5, 2024 · 1 comment
Labels
bug Something isn't working

Comments

@RogerZhang-CatapultSystems

If possible please send email to me and I can share the credentials to let you triage.

Expected behavior

Get-PnPClientSidePage should return the modern page object for all sites. instead of in some tenants' root site collection, the modern pages exists, but Get-PnPClientSidePage will always throw not exist error.

Actual behavior

Page 'XXX.aspx' does not exist in root site collection.
Note: We have three SharePoint Environments, the two tenants met not exists error in root site collection. For non-root site collection it works well.

Steps to reproduce behavior

image
image
image

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

Tested in both 1.12.0 and latest version 2.3.0

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

  • Windows
@RogerZhang-CatapultSystems RogerZhang-CatapultSystems added the bug Something isn't working label Jan 5, 2024
@RogerZhang-CatapultSystems
Copy link
Author

Closed the issue as found the root cause and submit issue in PnPCore pnp/pnpcore#1343

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant