Jul 22 2016 06:30 AM
So it's been asked many times in the old network and never answered, so want to ask it here in the hopes that people are actually thinking about this.
What is the plan for "modern" Document Sets in the new modern SharePoint?
Right now, the experience is you are in the modern UI for the doc library, click the document set and it takes you back to the old UI, in a very disjointed experience.
Document Sets are the most used feature in our environment (and I think one of the most powerful/useful tools in all of SharePoint).
Critical success factors in my opinion:
Things we typically add in code:
Sep 16 2016 03:43 PM
Hi 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!
Sep 19 2016 01:34 AM
Is there any rough timeframe on this?
I was seem to stumble upon little things that make usage for a user very weird.
Dec 06 2016 12:17 AM
I'd like to bump this thread again, since there hasn't been any information (or I haven't found them yet) on document sets at Ignite and nothing since then either.
I've discovered a few issues with document sets and their behaviour and even some showstoppers than make working with them impossible
Dec 06 2016 06:51 AM
Here is another question I asked during the AMA that didnt get traction either: https://techcommunity.microsoft.com/t5/SharePoint-AMA/When-will-we-see-Modern-Document-Sets/m-p/2903...
Document Sets, Search Web Parts, Publishing-Style Navigation (with audiences/permissions), and List/Library web parts are all the primary missing elements (what I would consider sharepoint staples) that are preventing us from even considering rolling out modern SharePoint at this point
Dec 08 2016 07:14 PM
Since Modern team sites were introduced I have 'more or less' abandoned Document Sets except for specific use cases where they are useful. They were already too hard to set up let alone add (New Document - Document Set). They are even harder to add in the new look. Folders are so much more obvious to users but their use will only replicate the file share structures on SharePoint.
Dec 27 2016 05:18 PM
Thanks for the feedback. Document set content types are supported inside modern document libraries. The intent is that these content types show up under the New menu in modern, and clicking a document set takes you to the classic document set homepage with all functionality intact.
For the bugs you specifically mentioned:
Now, even if this experience was totally bug free, we acknowledge that having classic document set welcome pages within modern document libraries is a disjoint user experience. We want to bring the document set homepage, and all the functionality inside, to the modern world. This is on our backlog, but I can't guarantee we'll get to this item in CY2017.
Dec 29 2016 06:26 AM
Jan 08 2017 01:15 PM
Thanks Lincoln.
You said you 'can't guarantee we'll get to this item in CY2017'. If (as I expect) we roll out SPO to our users during 2017 replacing their SP2013 on-prem experience, the relative inaccessibility of document sets will hasten their disuse in favour of folders in our environment where Site Owners created document libraries.
Document sets will remain useful in specific cases.
Jan 08 2017 10:21 PM
Jan 10 2017 06:40 AM
Jan 15 2017 08:43 PM
Thanks @Brent Ellis, we've had SP since 2012 and it's used across the organisation (of 8,000 staff) in various ways. We have remained very much OOTB since then, which has facilited upgrades. Reading what is happening to connect O365 Groups and SPO sites means on the one hand that we need to keep things fairly generic and vanila for users, but I'm sure we'll find reasons to retain existing DocSet-based libraries in specific areas. As always with SP, there is a balance of control involved - we have 'light' control (with only 2 admins) and Site Owners take responsibility for configuring their sites.
Jan 25 2017 12:05 AM
Hi All - Non-technical user here (but still in charge of our IT area!). Scary but true.
So, we have a current Intranet site, quite basic, and based on the "classic view". We're keen to use SharePoint more and because we don't have legacy issues, we can switch to the "modern" version with really no issues to speak of.
However, reading alot about the benefits of Document Sets, and the fact they don't exist yet with the modern experience, can anyone give guidance on how best to approach document management NOW (using modern experience) with an eye towards making sure the approach is "upgradable" if/when modern document sets becomes available? In other words, what approach would you use in this situation to help future proof our users' experience?
Jan 25 2017 12:13 AM
Jan 25 2017 12:15 AM
Jan 25 2017 06:36 AM
Feb 23 2017 08:44 AM
It seems they have been making some changes recently (1/2017) with the Document Set "modern' interface. It no longer defaults to Classic, but the tagging/information panel doesn't work. They even added an edit all link in the Info Panel but it just takes you to the Doc Set title. The only way I can see to edit Doc Set tags is in the Quick Edit. And the New tool bar is missing the link option. So now it is in the half-way house. At this point I need to set all Doc Sets to Classic view :-(.
Can someone please create a User Voice as suggested. This is having a significant impact on existing users and I'm not sure if I should be including Doc Sets in new designs.
Feb 23 2017 10:39 PM
Dear @Lincoln DeMaris,
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.
Feb 24 2017 09:48 AM
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
Feb 12 2018 02:08 PM
Solution