Forum Discussion
What is the plan for "modern" Document Sets?
- Feb 12, 2018Its 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.
For the record, it is not entirely levity - I think quite a few of us are quite frustrated by repeated broken promises. Let's hope it really is good and not full of bits that aren't implemented yet and still require classic.
I was reading the "SharePoint online" documentation yesterday and was shocked at how many times a feature was described for modern (e.g. mega menus, global navigation [the article on that finishes with "Global navigation is not yet available"). only to say it isn't done. There seem to be so many scenarios in which the documentation tells us effectively not to use classic (pointing out the pitfalls) and then talks about solutions in modern that aren't available!
I think it has reached a special level of frustration for all when even those writing documentation feel the need to describe features that don't exist as some kind of cover or justification for the product.
There is an element in which it is helpful to highlight the direction of travel but with few honest/realistic statements as to implementation dates, the effect is to paralyse customers. I suspect that there are many out there who bitterly regret delaying projects in anticipation of the "coming soon", "this year", "next quarter" document sets.
(I have sympathy - I have been in IT for 35 years - and spent 20 years as an internal vendor with MS) but your team must have been aware of slippage way before you told us.
Just making sure the fine folks on this thread saw our latest announcement on this topic yesterday:
Update: Document sets in modern document libraries
My apologies for the repeated delays. We are really confident in the new May date!
- John WynneMay 23, 2019Silver ContributorNo I haven’t needed to try that Ivan. Copying @ChrisMcNulty for his thinking. Though I’m sure he’s busy this week ;-)
- Ian CunninghamMay 23, 2019Iron Contributor
Good - I must be cursed. 4 office 365 subscriptions and I don't see this in any of them yet... I guess it is just something to do with being on the far spiral edge of the galaxy?
- Ivan54May 22, 2019Bronze ContributorHi John Wynne,
Have you tried using grouping of document sets with 2 levels yet? 1 level seems to work though.
This isn't working for us anymore. Columns are managed metadata columns. - John WynneMay 22, 2019Silver Contributor
Ian, Document Sets are definitely rolling out! I don’t think any conversion is necessary...
- Ian CunninghamMay 22, 2019Iron Contributor
Hi
I note that the document in the link refers to roll out early May. As June is now almost "bustin' out all over" have I missed it? Or do I have to do something to change my existing document sets in otherwise modern sites?
- DudditzApr 27, 2019Iron Contributor
Looking forward to using these,
Something to consider,
Within the enterprise document handling is often tied to a Customer, project, etc. generated from a LOB system. Often this data exists upstream so it would make sense one would wan't to generate the document set, folder, etc. from an upstream process rather than a manual process within SharePoint. I would really like to see the ability to be able to create Document sets & Folders directly from PowerApps. In my opinion most organizations rarely start their enterprise ECM processes from within SP and often begin well before we get to SharePoint. This would really take Document sets to a new level. Currently to do this you have to use a variety of work around's by writing your values to a SharePoint list and 3rd party tools to finally take the values and generate a Doc Set.