In OneDrive there is a limit of file path which allows only 260 characters. This killing our file storage structure. It should support more
In OneDrive there is a limit of file path which allows only 260 characters. This killing our file storage structure. It should support more character or count file name as path not all folders.
Matt Wiedemeier commented
260 and 400? HAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHAHA!!!! Don't worry, Google allows 32,767 characters.
Gary Turner - ManageTech commented
The path structure created is further challenged by the STUPID use of the M365 Tenant name in the local path. Lets imaging you are that well-known lawyers "Weadon, Bassett, Hampton, Hughes and MAcKenzie Lawyers LLP", Do I change the Tenant name and upset one of the partners or should MS just not use the Tenant name.
Additionally then we add the sharepoint site name or Teams group and suddenly we can only save files called A.txt, B.txt as we are always out of characters. Don't just make the path longer get rid of the poor use of organisational names also.
I understand this is a operating system limitation however, this is a fairly big inconvenience. Please don't give up the pursuit for a solution.
It's very annoying and hindering our work. We need to get this fixed!!!
Matt Gudites commented
The "path too long" thing has been going on since the early SharePoint days, and this DESPERATELY needs to get fixed. This, plus all the other "SharePoint threshold" nonsense that comes along with. This is an enterprise tools and shouldn't have these limitations!
This is a very annoying problem, and the work around, while easy, is time consuming. What’s worse is that the Microsoft techs wasted countless hours of my time over several weeks to discover that it was a known problem that they could not fix.
Engineers should address and fix this.
Caitlin Boake commented
Voted, the 260 character limit makes the SharePoint document libraries synced with OneDrive significantly less usable.
Jeongmin HONG commented
Voted. My understanding was a limit of 400 characters in the SPO when we are using SP Migration Tool, however, since there are a lot of subfolders, the longer limit the better
Kaetochi Nwachukwu commented
Kristy Hudson commented
This is causing significant issues with my using OneDrive and has prevented me from moving important files into the workspace. I welcome any solution to fix it.
James Curran commented
I can’t believe this is still a thing. It has course so many problems, not just in One Drive but over the years, with the Shared Drives and on and on. It’s the single biggest issue I have with Microsoft
OneDrive Sync/Office Applications can only open/save up to 260 characters (218 for Excel). This is absolutely killing us because SPO expanded their limit to 400 characters. Any file/folder exceeding 260 characters in SPO can't be opened properly or saved into in file explorer view and we're getting the hit for this.
It's great you've expanded the limit in SPO, but why would you not make your desktop applications follow suit?
Rob Nicholson commented
I can't believe this one isn't near the top of the pile!
Steven Chackowicz commented
I agree. With business as complex as it is, with many having multiple areas of effort, having a relatively small character limit of 260 is unhelpful. The error message that displays is equally unhelpful and makes no mention of the limit thus forcing me to waste time to see if I had some character within the path that is not permitted - even more frustrating. Many years ago the limit for file names was 8 characters - one reason why I preferred Macs. Don't make me go back.
They should fix this, if you think; the beggining (C:/user/user/Business/ecc...), and arriving to the sixth level of folders (totally reasonable), let say 25 characters each level (totally reasonable), we already have ~210, leaving just 50 character in case of SharePoint Server, for the file name assuming that no other level of folder will be add (very unlikely). I don't know why it doesn't allow it, if the code of SharePoint, I don't know, but please fix it..