Allow files that have special characters in the name to be uploaded
This makes it hard to convert users in our company.
You can now use # and % in file and folder names on OneDrive for Business and SharePoint! Learn how to enable this in your tenant and more here: https://techcommunity.microsoft.com/t5/SharePoint-Blog/New-support-for-and-in-SharePoint-Online-and-OneDrive-for/ba-p/60357 . Thanks!
Same here! Every other application can handle these so-called "special characters". For me this is a big deal breaker. Indesign makes a .idlk file which has a tilde at the beginning of the file name. Because of that i can't open indesign-files within Onedrive - Sharepoint and i have too copy the file too my desktop and then re-save it again....
Please make this work!
Come on Microsoft these are not special characters, they are normal characters in file names on your operating systems all over the world.
And as also pointed out elsewhere - it's not good enough to have a webpage somewhere that documents what is or isn't allowed, that you might find after googling the error message that certain files generate. Think harder. Much harder. Dropbox, GoogleDrive, even LiveDrive are wiping the floor with you guys simply because their software *works*
this really needs to be sorted, it's wholly unacceptable that perfectly normal NTFS filenames cannot be synced in ODFB, and as plenty of other commenters have pointed out often software generates filenames that cannot be changed, if the filesystem accepts those names then ODFB needs to as well.
This is a dealbreaker for me too - I must be able to sync files that contain # and % in the filename. It's ludicrous that a business-oriented cloud storage app like ODFB would not support this still in 2016. Even the personal OneDrive app does support such characters, and of course Google Drive, Dropbox etc does too. Please fix this with utmost urgency!
The # character isn't that special... all legal ntfs characters should be legal here.
graeme kelly commented
Using One Drive OS X client... a lot faster than BackBlaze but the character restriction is worrying.
I have 199 file naming problems with my OneDrive and to change them and relink the files into my projects is too much.
Please fix. The Cloud is meant to make things easier ?
wow. i just subscribed and now we might reconsider. i have thousands of documents that have special characters in them and they won't be able to be saved in OneDrive...how stupid is this???
Think about it...harder. We want to move over from Dropbox, and are finding the workarounds a deal-breaker.
I was about to subscribe to Office 365 and use OneDrive to back up all my Logic Pro X files, but it's refusing to back up folders/files as they have the wrong characters. What a wasted oppertunity. I get no problem with Google Drive.
Is there no work around? As somebody else said, you can't change file names in Logic Pro X as it will corrupt the project.
Doron Friedlander commented
Glen, the underscore isn't restricted. It's true that the groove based ODFB sync client does sometimes experience issues with the underscore. You can completely bypass that issue by using the NextGen Sync client(NGSC). The only draw back with the NGSC is that currently it cannot sync to SharePoint team sites, but this feature is being worked on and is expected to be released within the first quarter of this year.
Here are some helpful links:
OneDrive for Business Next Generation Sync Client is now available for deployment. See the following blog for more information:
Restrictions and limitations when you sync OneDrive for Business libraries by using onedrive.exe - https://support.microsoft.com/en-us/kb/3125202
Deployment package for the new OneDrive sync client on Windows - http://go.microsoft.com/fwlink/?LinkId=717805
Deployment package for the new OneDrive sync client on Mac - http://go.microsoft.com/fwlink/?LinkId=717806
Get started with the OneDrive for Business Next Generation Sync Client in Windows/Landing Page - http://go.microsoft.com/fwlink/?LinkID=717725
Get started with the OneDrive for Business Next Generation Sync Client in Windows - http://support.office.com/article/615391c4-2bd3-4aae-a42a-858262e42a49
Get started with the OneDrive for Business Next Generation Sync Client on Mac OS X - http://support.office.com/article/d11b9f29-00bb-4172-be39-997da46f913f
Deploying the OneDrive for Business Next Generation Sync Client in an enterprise environment - https://support.office.com/en-us/article/Deploying-the-OneDrive-for-Business-Next-Generation-Sync-Client-in-an-enterprise-environment-3f3a511c-30c6-404a-98bf-76f95c519668
Transition from the existing OneDrive for Business sync client - http://support.office.com/article/4100df3a-0c96-464f-b0a8-c20de34da6fa
Deployment and administrative settings for the new OneDrive Sync Client (Mac) -
OneDrive Administration Fast track page (links to all content) - http://support.office.com/article/54ee4ad1-cf60-4294-9566-48824b491ff8
Doron Friedlander commented
Erick, it is not 2 conventions for 1 for server and 1 for online! It's on convention required by windows and another required by SharePoint. What you will notice is that the more restrictive set of character limitations, on the right, applies to SharePoint Server. It's not a function of the Online service. The restricted characters are based on SharePoint limitation with some characters that SharePoint misinterprets. This applies to both SharePoint Server and any online service that leverages SharePoint Server. I am including the link for one of Microsoft's support documents on this topic. If you look at the bottom it clearly mentions SharePoint Server.
Erick Sodhi commented
If a character is legal in a Windows filename it should be legal in a filename stored in SharePoint (including OneDrive for Business). I realize that this is a legacy issue because of the SharePoint/IIS platform, but it needs to be fixed. Users shouldn't have to deal with two file naming standards, especially when migrating from on-prem file servers and using processes in which characters that have previously been valid all of a sudden become invalid due to a migration to the cloud. It's obstacles like this that leave a sour taste in the mouths of users and result in a not-so-great attitude when it comes to talking about the cloud among their peers.
Glen O'Riley commented
This is a ridiculous restriciton! I've removed percentages and may other wildcards but now I cannot even use a simple plain ordinary underscore in my file names lest it be marked invalid. WHY would you not realise an underscore is a fundamental part of many naming schemes now?
Save a webpage in Internet exploder as well and there is a mywebsite_files folder is added and now is unable to be synced. Bloody hopeless when you cannot even support YOUR OWN naming conventions!!!
All legal characters for Windows filenames and directories should be allowed -- period.
The point is not whether the restrictions are publicly known or not, it's whether they make sense. With the new sync client, people want to treat ODFB like a drive / filesystem. When I receive a document called RFP#2015-2323-3.docx, I want to be able to drag it to my ODFB and be done. I can; it just won't sync. I know enough to edit the file name to fix that, but most users don't. So it goes unloaded, unshared (if in a shared folder).
Others have commented on the _files folder used with most "save as html" situations. Here, renaming the folder isn't an option at all as it breaks the html.
Bottom line: ODFB is the *only* cloud storage service with such silly restrictions and inconveniences.
Edward Dumser commented
I guess we're back to the DOS times, is there an 8.3 character limit as well by chance?
Paul Martell-Mead commented
The problem here is not the files and folders that Windows doesn't like but the ones which are perfectly legal on a Windows file system. Specficially, # in filenames and _files folders.
Lots of people save HTML pages to disk. Often its a order they placed. When you save from e.g. Chrome you end up with an HTML file called something like "Order #21292.html" and an associated _files folder containing the assets from that HTML file. Onedrive can't handle either. If I script a rename, then the HTML file breaks. Now I have to script editing the HTML links inside the html file.
Character limitation is a real deal breaker for my business. We share Logic Pro projects and as Miguel said, Logic uses some of these "invalid" characters in filenames that cannot be changed without ruining the project. It's a shame because in many other ways OneDrive is superior to Google Drive. OneDrive uses lot less CPU power, and the iOS app i better too, Googles iOS app is very laggy.
Doing some proof of concept testing right now and running into the # and % limitation.
Windows NTFS already has a restricted character set vs the other supported desktop platform of MacOS. Adding additional character limits will likely be a deal breaker for my users.