07-22-2016 06:30 AM
07-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:
09-16-2016 03:43 PM
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!
09-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.
12-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
12-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
12-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.
12-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.
12-29-2016 06:26 AM
01-08-2017 01:15 PM
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.
01-08-2017 10:21 PM
01-10-2017 06:40 AM
01-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.
01-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?
01-25-2017 12:13 AM
01-25-2017 12:15 AM
01-25-2017 06:36 AM
02-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.
02-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.
02-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
03-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
03-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.
03-10-2017 10:54 AM
03-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.
03-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.
03-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.
04-16-2017 07:26 AM
05-02-2017 02:49 PM
05-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.
05-19-2017 04:12 PM - edited 05-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,
05-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...
05-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.
05-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?
05-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.
05-23-2017 08:36 AM
05-23-2017 09:10 AM
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.
06-18-2017 03:49 PM
I know most of this thread is taken up with the modern v classic UI. However I'd like to post a 'wishlist' feature to tac onto Brent's original comment.
I'd like to see an option for 2-way updates of shared properties, such that an update within a document to shared properties flows back up to the doc set. Current property updates to shared properties flow from the doc set.
A current scenario is where we have stage payments for a project. In this scenario, there are always 4 stage payments, which are shared properties. The stage payments are calculated in an Excel spreadsheet, which is one of the default documents in the doc set. A macro updates server properties, so at least we get the stage payment amounts into document properties. It's then a manual task for the user to update doc set stage payments. It would be very useful to cascade those updates automatically back up to the doc set.
Can anyone suggest a way to do this in O365?
Expanding the thinking a bit, it would also be nice to be able to:
* Be able to set a property as updateable
* (Easily) share office objects for use between office docs in a doc set (kind of like what you can do with the new document assembly feature of Nintex and Intelledox)
08-09-2017 03:30 AM
After nearly a year of lookign closely do you have any news?
This really hurts - I have a very untehncial user base and the flipp betwen UIs is bafflign to them and hodlign up adoption. (There is talk of other technology e.g. bespoke meeting apps for goverment)
08-13-2017 04:55 AM
And no information either - seriously worried that the long delay means that a stupid decision is going to be taken here. Realistically how hard could it be to change the default colour and add a few buttons from existing modern libraries?
08-14-2017 12:58 PM
As with all things content services related, there is a long term plan to update and advance the cause during the coming months and beyond.
I know its taking us longer to address modern docsets than it might seem, but please know that we are working diligently to complete the lingering classic experiences that are not yet represented in the "modern" user experience. We are using telemetry on user frequency to help shape the order of operations and document sets are definitely coming. Not by Ignite, not close enough yet that we have a public date for it, but coming...
08-15-2017 02:18 AM
Good to hear this is not going away as it is one of those elegant things that is just the right solution when it is needed so whether telemetry says it is not used by everyone, those who need and understand it, need it.
Still at least this has a workaround... training for the users and posting stuff to some of the older councillors who are already techophobes and take the view that the experience is too complicated when the world chabges from screen to screen.
Now all I need is a fix from the bug by which a lookup coulmn embedded as Document property in Word returns the item index number not the data in the coumn!. Elsewhere I have another MFST post with "we are aware" but have no ETA type response as though that is good enough ... it's broken, you sold it saying it worked the customer wants to know about fixes. Our service partner has reported that engineering has declined to fix it (showstopper for us as the lookup is a list of committees and every document we issue comes from a committee -we are local government).
Researching I see this was reported as early as 2014 but no update, no news - but the monthly bills for the software come in without fail.
08-15-2017 10:47 AM
I feel that changes over the past few months for Doc Sets have been a great improvement - much more consistent with modern UI. I have just finished a handful of webcasts for a client and unfortunately have to explain the differerent UI for things like tasks, doc sets, etc., but they don't seem to really notice - SharePoint is new to them so that's just the way it is.
08-15-2017 10:51 AM
08-15-2017 01:35 PM
We opened a tikcet via the admin and were contacted by our support partner who replied that issue was confirmed but that enginenring had declined to provide a fix.