We need to add the prefix as well to check whether it hits the 260 limitation. That’s why my previous test result of the part of the URL limitation is around 157. With the related team, the file path showing in the error message is only part of the complete URL, and the limitation of the complete URL (with the prefix “” that hidden in the error message) I’m sorry for the confusion these two limitations have caused. The 400 characters limitation of creating and syncing your files and the file path length limitation of saving a site as template are two different things. I understand your feeling, and that you created your files within the 400 limit. I’m very sorry for the inconvenience this has caused. If you feel a reply works for you, please kindly vote or mark it as it will be beneficial to other community members reading this thread. SharePoint Sites and Collaboration forum in UserVoice, it's designed for the users sharing their suggestions and requirements with the development engineers so that they could add or modify features according to the feedback. If you are not contend with just shortening the path, I'd like to suggest posting your request of lifting the Save Site as Template character limit to be above 157 in the I gave you these suggestions not because they are easy to make, but because I have tried other ways and these are the solutions that worked on my side. Is the shorten the template/library/folder name. Since this is a limitation of service, rather than a setting, I tried to figure out the actual limitation, by multiple tests, then again I found that if you want to keep the name of files unchanged, the only way to successfully save the site as template But obviously, by our test we already know that saving a site as template has another limit, although this isn't mentioned Yes, the article mentioned the 400 characters limit, which is actually proved on your side: because this is a limit of creating documents. But as both the classic sites and the modern sites have the same limit, this should be not so relevant to our real concern, the characters limit. And that's why I though youĪre using a classic SharePoint Online site with a modern UI. That by default the "Save site as template" option doesn't exists in Site Settings, you would need to run commands in PowerShell to enable this feature, while in a classic SharePoint site this feature already exists when created. I assume that your are saving classic site because per my test, I found All the suggestions that I provide you are based on my many tests. Everything I'm trying to do, is no more than do my best to help you. I feel very sorry if you misunderstood my words. It makes it very hard to use as a business tool.
I'm deeply frustrated by SharePoint online, the lack if support and the constantly changing landscape. It would mean folder path and file names that no longer make sense or canīe easily searched for as I'm sure you can appreciate.Ĭan you advise if you're knowingly publishing incorrect figures and why? Or perhaps the 400 limit refers to something else, if so can you enlighten me? I can also work out for myself that shortening the various part of the file path to below 157 characters would work but as I have explained this would not be a practical solution. Thirdly I understand how SharePoint is allocating the character limit - it should not matter if the published limit was correct. If you exceed that limit, you'll receive an error message." "The entire path, including the file name, must contain fewer than 400 characters for OneDrive, OneDrive for Business and SharePoint Online.
Secondly, as I have already said - your published figure is 400 characters not 157. I'm pretty surprised by this response and find it quite insulting.įirstly, as I mentioned, I am trying to save a modern site s a template not a classic site that you referred to. Is there another way to duplicate the site? If the character limit is 157 and SharePoint is going to use about 150 of those characters I have little to no room to play with in terms of file names or even folder names. Hoping the development team might change it in the future isn't going to salvage this project which has been carried out with SharePoint The main point is our file names are fine but SharePoint has created huge file names to suit it's own design rather then the needs of the user.Ī change in the future won't help our organisation now and I stand by the fact that the published figures say 400 characters. Of 1400 files I think 60% are now too long and identifying them will take quite some time. We can not alter the file names as they will no longer make sense or be searchable in the correct way. However, we're using the modern experience and the published figure is 400 characters.
0 kommentar(er)
