You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Many bugs reported are actually related to the PnP Framework which is used behind the scenes. Consider carefully where to report an issue:
Are you using Invoke-PnPSiteTemplate or Get-PnPSiteTemplate? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/pnpframework/issues.
Is the issue related to the cmdlet itself, its parameters, the syntax, or do you suspect it is the code of the cmdlet that is causing the issue? Then please continue reporting the issue in this repo.
If you think that the functionality might be related to the underlying libraries that the cmdlet is calling (We realize that might be difficult to determine), please first double check the code of the cmdlet, which can be found here: https://github.com/pnp/powershell/tree/master/src/Commands. If related to the cmdlet, continue reporting the issue here, otherwise report the issue at https://github.com/pnp/pnpframework/issues
Reporting an Issue or Missing Feature
Set-PnPDefaultColumn does not properly error out on folders with illegal characters. Attempting to set a default column value on a folder with an certain characters in the name appears to complete successfully, but does not set a value. It appears the error handling in this cmdlet does not include all illegal characters.
Expected behavior
The cmdlet to throw an error if attempted to run on an item containing illegal characters.
Actual behavior
The command appears to complete successfully but no values are set or changed.
Steps to reproduce behavior
Run Set-PnPDefaultColumnValue on an item whose name contains any of the characters listed below which are not currently defined in error handling.. Only { '#', '%' } are currently defined. This issue was found with item names containing apostrophes and ampersands.
Notice
Many bugs reported are actually related to the PnP Framework which is used behind the scenes. Consider carefully where to report an issue:
Invoke-PnPSiteTemplate
orGet-PnPSiteTemplate
? The issue is most likely related to the Provisioning Engine. The Provisioning engine is not located in the PowerShell repo. Please report the issue here: https://github.com/pnp/pnpframework/issues.Reporting an Issue or Missing Feature
Set-PnPDefaultColumn does not properly error out on folders with illegal characters. Attempting to set a default column value on a folder with an certain characters in the name appears to complete successfully, but does not set a value. It appears the error handling in this cmdlet does not include all illegal characters.
Expected behavior
The cmdlet to throw an error if attempted to run on an item containing illegal characters.
Actual behavior
The command appears to complete successfully but no values are set or changed.
Steps to reproduce behavior
Run
Set-PnPDefaultColumnValue
on an item whose name contains any of the characters listed below which are not currently defined in error handling.. Only{ '#', '%' }
are currently defined. This issue was found with item names containing apostrophes and ampersands.['"', '*', '<', '>', '?', '/', '\\', '|', '.', ':', "&"]
What is the version of the Cmdlet module you are running?
2.12.0
Which operating system/environment are you running PnP PowerShell on?
The text was updated successfully, but these errors were encountered: