Forum Discussion
New 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 allo...
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
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
$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
- Yeap, it needs some time what it's normal because you are modifying a tenant setting :-)
HI Peter,
Tenant updattion took 2 hrs.
Now we are able to sync items which contains # and % characters.
I believe 30-40% synchronization issue automatically resolved by allowing thes characters.
- Other than long paths though I assume
- Fingers crossed it works for us then
Out of interest have any of you heard about them extending the path length as per the other post on here?
I don't want to spend ages reducing path lengths so that we can migrate to then find it gets extended soon afterwards anyway.We have extended the path to 400 characters
