SharePoint 2013: Folders are bad

You have probably heard this SharePoint slogan before: Do not use folders with SharePoint. If you are wondering why this is or need some arguments to convince a customer, then use the following list of reasons.

1. Structure
Changing a folder structure is complicated and time consuming, while changing a metadata structure is easier.

2. Authorization
Setting authorization on folders is possible but before you know it you have created an administrative nightmare

3. Findability
A nested folder structure is only know to the person who created it. Nesting folders will result in semi hidden files.

4. URL length
The URL Length is limited around 256 characters. All the nested folders names will be added to the URL which means you will run into the 256 limit very fast.

5. File Path
When moving files between folders will change the files path. This can result in broken links to the moved file.

6. Duplication
Multiple copies of one file tend to end up in multiple folders. This will result in version conflicts and possible misinformation.

7. Navigation: The user experience with navigating through folders is time consuming and confusing. It is hard to remember where you are and which folders you already checked.

8. Navigation
When a few sub folders down it is very hard to see where you are in the folder structure

9. Filter
You are able to filter within the opened folder, you are unable to filter all the document simultaneously. Filtering all documents simultaneously will speed up the searching process.

10. Sorting
You are able to sort within the opened folder, you are unable to sort all the document simultaneously. Sorting all documents simultaneously will speed up the searching process.

11. Losing files
When you place a file in a wrong folder in a lot of situation you know lost a file.

12. Forcing groups
Files can fall under multiple groups, with folders you need to store the file twice.

Share

6 Replies to “SharePoint 2013: Folders are bad”

  1. Are you absolutely sure about the ~256 character limitation in SharePoint 2013? I can not find this stated anywhere. Only for Sp2010 and older.

  2. I am not absolute sure on the number ~256 but there is a limit. I have encounter it on SharePoint 2013 though. Errors saying the URL path was to long.

  3. Thanks! I am trying to source any official number from Microsoft. Not successful so far. But if you have encountered the error in SP2013 then there must be a limit at least.

  4. I was unable to find it in an official source. I got this number from multiple blogs. That is why it is stated as ~. If you find an official statement, if you would be so kind to link it here. Thanks and good luck.

  5. The 256-character limit is an HTTP URL limitation, not a SharePoint-specific limitation; that is probably why Microsoft hasn’t bothered documenting it as a SharePoint limit.

    The document ID service does not remove the 256-character limit, but it allows documents to have GUID-based URLs that are not dependent on their site/folder locations. The idea is that you can have a link to a document that will always work, even if the document is moved to a different folder or library. That the GUID-based URLs are shorter than the 256-character limit is just a serendipitous perk!

Leave a Reply to BP Cancel reply

Your email address will not be published. Required fields are marked *