Bug when setting "DenyAddAndCustomizePages" on the site properties.

[acmurchison-il]

Category

• Bug

Describe the bug

When setting the "DenyAddAndCustomizePages" on site properties, it's throwing a PnP.Core.CsomServiceException with the message "The requested operation is part of an experimental feature that is not supported in the current environment.". The value is actually set in SharePoint but we shouldn't be getting an exception returned. Potentially is a Microsoft update that is making this occur.

Both settings cause an issue:

Steps to reproduce

When calling the 'Update' method it throws the exception PnP.Core.CsomServiceException

Expected behavior

No Exception is thrown when it successfully sets in SharePoint.

Environment details (development & target environment)

• SDK version: [Pnp.Core 1.14.0]
• OS: Windows 11
• SDK used in: Reproduced in Test Framework (.NET 8.0, Console Application). Also seeing in an Azure Function.
• Framework: .NET8.0
• Browser(s): null
• Tooling: VS2022
• Additional details:

Additional context

Thanks for your contribution! Sharing is caring.

[fzbm]

We had the same issue and switched back to CSOM for this, because there it is still working. Our production environment was affected and we needed a solution for this issue fast. What we also determined is, that even if the error occurred, the state has still been changed. Nevertheless this issue should be looked into and getting fixed.

While PnP Core uses hand crafted CSOM requests for this, it looks like there is still a difference between the requests of the original library and PnP, which then triggers a different path on the server.

[ajcaterino]

We are also seeing the same issues when setting Site Collection properties. We set the StorageMaximumLevel and the value is not saved.