Forum Discussion
MicrosoftNew support for # and % in SharePoint Online and OneDrive for Business
In the upcoming weeks, we’ll be shipping support for # and % as supported characters in file and folder names across document libraries in SharePoint Online and OneDrive for Business. This will allow people to create, store, and sync files containing # and % characters whether those characters are used as a prefix or suffix to the file or folder name. # and % will be limited to use in file names in addition to SharePoint Online and OneDrive for Business document libraries and related folders.
More information here: https://techcommunity.microsoft.com/t5/SharePoint-Blog/New-support-for-and-in-SharePoint-Online-and-OneDrive-for/ba-p/60357
- Awesome addition :-)
- Stephen Rose
Thanks! I will share this with our engineering team :)
Hooray at last... all of my clients in the finance sector will be very happy with this... I've been promising them it's coming for a long time now!
- Thats great as we are just planning our migration from Egnyte to OneDrive and have just come across this limitation, how will we know when it is now an option?
- Just seen on the other site that we still have a long wait then...
H2 CY2017 for existing Office 365 Tenants
Great news. I enabled this, this morning and it looks like it's working for us.
- How did you do it?
I just want to make sure as support have been no help for me so far and all that happens for me is that when I run the Get-SPOTenant/Set-SPOTenant it says that is not a recognized name of a cmdlet- Scrap that I found on the comments on the article the following script seems to work just need to give it some time.
$adminUPN="xxxx@xxxxxxxx.com"
$orgName="tenantnameinsharepointURL"
$userCredential = Get-Credential -UserName $adminUPN -Message "Type the password."
Connect-SPOService -Url https://tenantnameinsharepointURL-admin.sharepoint.com
Set-SPOTenant -SpecialCharactersStateInFileFolderNames Allowed
Our Office 365 admin - would like to know if there will be complications with future updates, if we run the powershell SpecialCharactersStateInFileFolderNames Allowed now?
- Stephen Rose
No. You should be fine. This is not a hack, it's a fix.
Thanks for you reply Stephen. Are there any points where we should be carefull it we run the fix? What is the estimatet rollout date in calendar terms, think month?
Stephen Rose, our use-case is completely the other way around.
We want to stop users from uploading documents with special characters. We are sick and tired of all kinds of weird filenames uploaded to our SharePoint libraries. Filenames that are a hundred miles long punctuated with all kinds of characters!
Is there a way to block all/selected special characters instead of allowing?
