Forum Discussion
What is the plan for "modern" Document Sets?
- Its too early to put specifics on the roadmap - but we will update document sets. We are not being "classic Microsoft" here - there is a steady stream of requests for docsets (along with other parts of classic ECM) and I've never pretended otherwise. Fear is not part of the plan. I hope to be able to give roadmap updates at SPC or Ignite this year, if that helps.
MicrosoftHi Brent,
We're looking closely at Document Sets currently. They get significant usage in the service, and it's clear that they're in need of a UX update. We want to make them great at what they're currently good at - managing a set of related files together. We will keep the "bones" of the feature intact - shared metadata, distinct content types, and customizable homepage. We'll likely add modern pages and page editing, modern library views, Flow integration, and other features that will help collaboration happen on files inside a set.
Thanks for your feedback!
Dear LincolnDeMaris,
Could you take a look at Julies comment as we're having the same issue at the moment.
Is this something that will get solved, or is the general guideline to force classic view for document sets. Previously at least modern ui worked at least half baked.
- LincolnDeMaris
Thanks for reporting. I'm working with engineering to get this fixed. One of the following should be true: 1. the modern property form for document set content types should show the document set metadata or 2. the property form for document set content types should always be the classic form
Dear LincolnDeMaris
any update on the metadata issue for document sets with modern ui? It's still not possible to edit other metadata for document sets, except the Name.
I have the same issue.
My users can only change the name, unless they force it to go back to Classic view.
I have now set the document library to always show in Classic view.
At least this way the users can work with Document sets
- Cool, thanks for the update!
