Forum Discussion
Why are we still hit by MAXPATH limitations in OneDrive in 2019??
According to this article, MAXPATH was increased to 400 characters (wow thanks) in SharePoint and OneDrive. https://techcommunity.microsoft.com/t5/Microsoft-SharePoint-Blog/New-MAXPATH-limits-in-...
It's very annoying as I'm having to defend my recommendation my client switches from DropBox Business to OneDrive. Okay, so Dropbox (et al) when working with File Explorer all have the same problem but OneDrive amplifies the problem with using a very long HTTP header.
Dropbox: C:\Users\123456790123\Dropbox
OneDrive: https://tenantnamehere-my.sharepoint.com/personal/onedrive_tenantnamehere_onmicrosoft_com/Documents
So 30 character pre-amble for Dropbox (12% of MAXPATH) but OneDrive 99 character pre-amble (40% of MAXPATH).
I tried to be clever and used a junction to reduce the path length and whilst it opens, it opens read-only and without autosave 😞
Plus I wondered if space replacement by %20 was also making it even more greedy in using up the MAXPATH limit.
- That URL MAXPATH is over 400 thou to make up for it. The local MAXPATH for onedrive is going to be c:\users\username\onedrive - orgname closer to dropbox's.
