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:
Mar 08 2017 05:19 AM
Dear @Lincoln DeMaris
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.
Mar 09 2017 06:29 AM
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
Mar 09 2017 01:52 PM
I've just stumbled across this thread because I'm looking at options for a client of mine, and Document Sets would be a perfect fit for them IF they worked fully in modern. Interestingly the behaviour I've seen tonight is when I edit the document set properties, I only see Name. However, when I hit the save button, the other fields briefly appear while the page is navigating away which means they're there, just not visible when they need to be. Seems like it's teasing me!
More interestingly, I've just dived into the DOM on the update form and it appears my fields are there, however the Knockout conditional switches are hiding it.
Mar 10 2017 10:54 AM
Mar 11 2017 03:24 AM
I'm having the same issues. Was actually rolling out a solution to a client that relied heavily on document sets and this broke just a few days before we rolled it out. They were really lookign forward to the new experience, but alas, we had to tell them they had to revert to using the classic UI until Microsoft could fix what they broke.
It's also not helpful when you have to give client the warning that b/c your in the cloud, Microsoft may randomly break key functionality with an update and there is not telling how long it might take to get said functionality back.
Hoping for a fix soon, the breaking of such key functionality and the slow response in fixing this has been dissapointing at best.
Mar 19 2017 07:38 PM
The inability to update Document Set metadata in the Modern UI is freaking out my users. Back to classic view for everyone. Hope classic view is supported at least until this issue is resolved.
Looking for an update on fix.
Thanks in advance. I know there are a lot of moving parts.
Mar 20 2017 09:42 AM
Thanks for your patience on the document set property bug, everybody. We have fixed the bug, and the fix is rolling out this week and next.
Apr 16 2017 07:26 AM
May 02 2017 02:49 PM
May 19 2017 03:55 PM
We just created an Office 365 Group, and then linked it to a new Team. Obviously this spins up a bunch of related resources, including a modern SharePoint site. Site Settings is really stripped down, and furthermore I don't see the ability to define a new custom Document Set content type there. Am I missing a button/config somewhere? Is this not available here? The Document Sets are handy at times for batch management.
May 19 2017 04:12 PM - edited May 19 2017 04:21 PM
Hmm - you are right.
This is not an encouraging sign, As you say document sets were a very good way of tagging together a set of documents, applying some common meta data and reducing the need for folders. Although the meta data approach is clearly "right minded" the limited filtering level in views mean that collection by other methods is still useful.
I have not been a heavy users of Sharepoint in production (i.e for me but not others) and now I would like to get on but I find the drawn out and incomplete nature of the transition together with a lack of definitive statements e.g. "do it this way now and you will OK in the future" very frustrating.
[I spent yesterday discovering bugs/holes in powerapps]. I find nearly everything seems to be half done these days,
May 19 2017 04:17 PM
Quick answer: This was definitely not intentionally removed. I will follow up and see what's going on here. Is the requisite site collection feature enabled? https://support.office.com/en-us/article/Create-and-configure-a-new-Document-Set-content-type-9db6d6...
May 19 2017 04:46 PM
Cool thanks! And good thought, I'll go and check the feature.
May 19 2017 04:51 PM
Excellent thinking, that seems to have done the trick, thank you!
May 19 2017 05:08 PM
Yes - on my main site it is "active". (the colection optios doesn't appear under site settings for the group s te). My libraries (modern or otherwise) in my main site do have this enabled and usuable but the sitethat was created by my outlook group although being in sites/ underer my main site does not have the feature and document sets does not appear in the list when managing content types.
May 22 2017 10:22 AM
Ian, I don't quite follow what you're saying.
Are you saying that when the site collection feature is enabled, the option to create a Document Set appears in libraries, but when the site collection feature is disabled, it doesn't?
Or are you saying that in some of your sites, you're not even seeing the site colleciton feature as an option to enable/disable?
May 23 2017 02:24 AM
I am saying that I see the option described on my "parent" (only) Sharepoint site (which has a URL xxxx.sharepoint.com) and it is on. When I look at the properties of the group site that was created by the outlook group (which appears in sites under our main URL) there is no such option. i have no idea whether the automatically creted site considers itself part of any collection but there is no option from the menu when "in" this site.
May 23 2017 08:36 AM
May 23 2017 09:10 AM
Correct
Only my original site has this.
Reading elsewhere I think I am told that outlook groups create a new site collection.
That said, my biggest concern is whether Micrsoft plan to support collections in the modern UI and if so in what time frame; the gradually shifting and unrpedictable UI has basically halted the adoption of sharepoint in my organisation.
If it's not hard to make the UI change, then the worry is that it not having appeared for so long could mean that there is a plan todrop the feature
And if it is hard, then there is dnager it will never happen because it is hard.
Colelctions seem to be the ideal tool to reduce folders in an evironment e.g. in our usage to "tag" all the documents associated with a particular meeting.