Forum Discussion
MicrosoftUpdate: Document Sets in Modern Document Libraries
thank you very much for that update. Tree days ago this update was rolled out to our company.
But there are two more issues now:
1. when I click on a document set, the link opens in a new browser tab. Is this intended by you or did I something wrong? It would be good to have the link open in the same tab!
2. our default view for the ducument library and inside the document sets are different. when I click on a document set and it opens a new tab, everything is correct. But when I have opened the document set and using the breadcrumb to go back, the view isn't switching to the default view of the document library!
I hope you can give me a solution for that.
Thanks a lot
Michael
lotz-hellerau and LincolnDeMaris
Another major issue:
If you had content types that were part of a document set, the modern experience has massively messed that up. Now the library and the document set seem to share content types. Within the document set if you go to New, the default is to re-add the document set content type, not other content types defined within a document set.
- After you add the doc set based content type to a library it takes a while for library settings to be fully updated, and for the content types included in the document set to be available via the New button. Until then you see the default New menu content types. It took about 40 minutes for this to update.
LincolnDeMarisLanceter Are you using content types that are syndicated from a content type hub?
- No, Linc, not in this case. This was a quick test in a stand alone site collection. Good observation!
Lanceter are you referring to the document set content type? Yes, that shows up at the library level under New as expected, but it also shows up within the document set. For example, I have a document set content type called "Case". In the library, I can go New--Case as expected to create the document set.
But once I'm inside a case document set, I only have the same options for the New menu that appears at the library level. But if I'm already in a Case I don't want to be able to create another Case document set. That makes no sense.
In my scenario I have a document-based content type called "Checklist" that is associated with the Case document set, not the library. Meaning the "Checklist" should show up under New when you are inside the Case document set. With this approach, different content types show up under New at the library level and also from within the document set itself. It works in Classic, but not in Modern.
Are you able to display different content types at the library level and inside a document set or do you only see the same options too? Just wondering if others have the same issue with content types inside a document set.
Sounds like inconsistent behaviour. I'm seeing different content types on the New menu at the library level and the New button within doc sets, as per the settings. It took a while (about 40 minutes) for the New button settings to flow through and be available within the doc set, and until then all I saw was the default menu you get if you aren't managing content types in the library.
The only other factor I can think of is that I configured the library and doc set content type yesterday, rather than it already being an existing library and content type.
At the library level:
...and within the Doc Set:
Here are the Document Set settings:
Another potential issue - in my case, the info panel doesn't display the MetaData associated with the Document Sets. I can see where the data is supposed to be but the area is just empty. These document sets do have a great deal of MetaData associated with them, but the info always displayed in classic just fine. It's not a timing issue either as I have given the pages several minutes to load.
rodieremix It's because the metadata/properties panel no longer shows up within the document set. It only shows up back at the library level. Which is a whole new thing for users who are used to Editing properties from within the document set. So essentially to see/edit the properties of your document set, you have to go back to the library level and select the document set [folder] to get the info panel.
- LincolnDeMaris
Hi all, I'm sorry to hear that many of you are having problems with document sets in modern.
- Move To/Copy To on document sets. The change that's rolling out does not enable any new move to/copy to scenarios on document sets. We hear this feedback and this is near the top of our backlog to address.
- Opening in a new tab. Before this change, document sets would open in a new tab in classic mode. After this change, they open in the same tab in modern mode. If folks are seeing document sets opening in modern mode in a new tab, that's very surprising - let us know for sure that the new tab behavior is indeed the modern document set view (as pictured at the top of this thread) and we'll look into this.
- Document set metadata. Document set metadata should be appearing in the details pane when inside the document set. If this is not happening, there's a bug we need to fix. If this is happening in your environment, please message me with the field types inside the document set content type and we'll try to reproduce, although your best and fastest recourse might be calling support.
- Document set views and content types. Document set views and content types as configured inside the document set content type should be respected. If this is not happening, we have a bug that we need to reproduce. Please send me more information in a private message - like what views and/or content types are present in the document set content type settings. A screenshot of the settings page could work wonders.
