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] Set-PnPDefaultColumn does not properly error out on folders with illegal characters #4712

Open
5 tasks
aefruswg opened this issue Jan 28, 2025 · 1 comment
Labels
bug Something isn't working

Comments

@aefruswg
Copy link

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. 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.
  2. 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.
  3. 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.

['"', '*', '<', '>', '?', '/', '\\', '|', '.', ':', "&"]

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

2.12.0

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

  • [X ] Windows
  • Linux
  • MacOS
  • Azure Cloud Shell
  • Azure Functions
  • Other : please specify
@aefruswg aefruswg added the bug Something isn't working label Jan 28, 2025
@NishkalankBezawada
Copy link
Contributor

I too had similar issue, with swedish alphabets. å ä ö

//Nish

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

2 participants