- \n
- For workspaces that contains document folders, typically workspaces whose documents have been migrated from a file server or from a document library where documents were structured using a folder-structure, these document folders will be displayed as document filters called \u201cFolder\u201d in the workspace\u2019s filter-zone.
![\"Document](\"https:\/\/metashare.com\/wp-content\/uploads\/image-546.png\")
<\/li>\n\n\n\n - The folder filter, as opposed to all other hierarchical document filters, will only show the specific documents that are located in the selected folder, not the documents in the selected folder\u2019s sub-folders. To see these documents you will need to drill down to the specific sub-folder.<\/li>\n\n\n\n
- A prerequisite to show the Folder filter is that the workspace\u2019s workspace configuration is configured to show folders.<\/li>\n\n\n\n
- As a folder structure can be quite deep, we now expand the width of the document filters, so that you can see the whole structure.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Changes to the document tasks\u2019 page<\/a>:\n
- \n
- Documents with missing mandatory\/required metadata were previously only shown in the document tasks\u2019 page for the user that last modified the documents. This has now been changed so that they are shown for all the workspace\u2019s members\/contributors.<\/li>\n\n\n\n
- If any documents were incorrectly added to a workspace as the standard \u201cDocument\u201d content type, e.g. documents that were previously moved and did not get the content type defined by the workspace configuration, they are now shown in the document tasks\u2019 page, as documents with missing properties, so that proper actions can be performed on them.<\/li>\n\n\n\n
- If all the available tasks in the document tasks\u2019 page<\/a> have been managed, the user will now be redirected from the task\u2019s page to the workspace\u2019s start-page. Previously users had to click on the workspace\u2019s name to get out of the \u201cTasks\u201d page.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Improved searchability:\n
- \n
- Earlier, when searching for a specific search-phase, only the 50 first documents matching the document query would be shown in the list. Infinite scrolling is now enabled, when you scroll down the list.<\/li>\n\n\n\n
- In large workspaces (workspaces with more than 5 000 documents), you can now search freely without the risk of hitting SharePoint\u2019s list view threshold warning.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Improved performance:\n
- \n
- In order to improve the performance in a workspace, when opening the document property form (creating a new document, uploading documents or editing documents\u2019 properties), the managed metadata terms and content types are now cached so that the next time you open a document property form in the same workspace, the loading time will be faster. This caching is done per user, per workspace and per browser session. In the next planned releases, we will be adding a few more features that will further improve the performance in MetaShare.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Increased the maximum number of columns:\n
- \n
- Previously a document could just have a maximum of 12 lookup columns (managed metadata and people-picker columns), preventing editing a document\u2019s properties, if this limit was reached. We have now eliminated this limit.<\/li>\n<\/ul>\n<\/li>\n\n\n\n
- Full error message:\n
- Improved searchability:\n
![\"Error](\"https:\/\/metashare.com\/wp-content\/uploads\/image-549.png\")
<\/li>\n<\/ul>\n<\/li>\n\n\n\n![\"The](\"https:\/\/metashare.com\/wp-content\/uploads\/image-548.png\")
\n