Enable long file path for OneDrive for Business
My 1GB of storage part of my Office 365 Business subscription is more or less useless because I get the "File name too long" issue with most of my files.
The following request is now closed as completed but I have voted on it with OneDrive for Business in mind (and I'm sure a lot of other other users did!).
So, OneDrive for Business users, make your voice heard and vote for this!
You can now use much longer paths with OneDrive for Business and Team sites! You can read more about it here: https://techcommunity.microsoft.com/t5/SharePoint-Blog/New-support-for-and-in-SharePoint-Online-and-OneDrive-for/ba-p/60357. Thanks for the feedback!
Almost lost my project because of it! (Files not uploaded!)
Fingers X for it!
When will this finally work, Microsoft?
Matt Godana-Lee commented
@Zach regardless of bad practice, there are occasions when file names are out of your control or do not fit work flows. In the real world, especially in AGILE/LEAN development worlds there are lots of different teams working on singular projects along each Sprint. Much like graphic development file names will contain more than just filename.ext it will have relative information to help progress the project such as: filename_date_version_status.ext or filename_date_lastedited_status or for production code testing dev_oneCoolScript_01012017_UATcomplete.bash
So its a knee jerk reaction to say, use smaller filenames, but in the business world, especially places where automation uses code to rename files or to fine and manage data, this isn't possible. Other vendors are able to do this, it makes NO SENSE that Microsoft can't make this work. They have an amazing product that essentially is like building the perfect track running then not allowing them to run with shoes on.
@Peggy this is a bad filenaming practice to begin with. I recommend finding a mass filename changer. There's one for mac called NameChanger.
Peggy Wardlaw commented
My biggest complaint is that files with # won't upload. Is there a way to delete that in all file names?
When is this going to be fixed?
It is driving me insane. In my company I have to use OneDrive for backup and I can't.
And I am not going to search for and rename 100 files to fix a bug that Microsoft has created for its users. I should not have to fix the problem created by Microsoft's not fit-for-purpose software!!
(Office 365, Mac Book Pro, MacOS Sierra 10.12.3)
Hurry up, i get a lot of bad comments from the business and management
Kayla Clark commented
What is going on has this been changed yet. I am trying to use onedrive for business. Please fix this !
Kayla Clark commented
Please MAKE ONEDRIVE FOR BUSINESS FILE PATH LONGER! THIS IS RIDICULOUS !
Please fix this.
I've been following this thread since June last year. Yes, this is the single biggest obstacle to any Office 365 sales case. Sharp tongues may claim that what value added is there to paying annual subscriptions to the Office Suite if you can amortise the cost over 3 years anyway? (The answer is online storage and file collaboration, i.e. OneDrive for Business and Office 365 Groups. Yet, right these two key features are massively gimped.) Given the salience of argument and number of replies, I am surprised that Microsoft has not been giving any clearer outlook yet. Is this usual? I wonder how difficult the change could be. @Microsoft: Can you shed some more light on this? I have users and budget sponsors to explain to alike.
This is probably the single largest obstacle preventing our company from completely migrating to Office 365, from current mix of Dropbox for Business + 3rd party email + Office licenses.
We have a highly structured storage repository with deep nesting. This largely works fine in Windows (7, 10), and is never an issue with Dropbox.
anything path I can use in explorer should be able on onedrive. NTFS supports some 10k characters - just get this limit off of the explorer and onedrive. Basically any other solution (on premise fileserver, NAS, google drive, dropbox) has no issues like this...
Sandy Wood commented
Add me to the mix. This is really a problem for us!
Migrating to O365 has been a huge step backwards for my company. Online storage (the main reason for us to change) is useless as I have no intention of renaming tens of thousands of files. We use the # symbol extensively in our file naming convention, which is not supported.
Not happy Microsoft...
Hurry up! My customers are waiting to get their (shared and private) files to OneDrive for business.
ANY legal windows file name should be supported. This is NOT a business ready product. Expecting users or domain administrators to rename and monitor potentially thousands of legitimate WIndows file names for length and special characters to support OneDrive's capabilities is ludicrous. File name length is not the only issue. Legal characters such as "#" break it too.
Ok, let's face it, this limitation is blocking a lot of customers. I do not want to defend Microsoft but if a product does not suit you , why you should hate , you can use another product.Furthemore, the Office 365 packages are extremely cheap , you get email/ODB/SPO/Office and many more for 15 bucks a month , come on.
Most people do not realize that this product has like hunders of functionalities and there is hardly any competitors. People hating Office 365 is like me hating my ISP because i pay 5 bucks a month for 55Mbps and i get 54.5Mbps or occasionnaly an issue. Think,Compare,Progress :)
adding my one cent :)
This is quite ridiculous.. I have stopped syncing the company data because of this issue as this does not allow a large number of our files to sync and we cannot have a partially synced business data! Please add this asap or we might have to migrate to other services..