Monthly Archives: July 2019

Content type view for Modern Document sets in SharePoint

We have the “Modern view” for Document Sets released !!!

Ever since the arrival of the modern pages and the modern lists/libraries in SharePoint, many of us were waiting for the modern view for Document Sets. This has finally arrived.

Here is the link to the official announcement.

Classic experience


Document Set Content type view

The above view inside a Document set is the default. Most of us know that this can be converted to something like this:


Notice the selection of the view as “Document View” and this view has a grouping of “Document Type” column, which gives a neat representation of the documents inside the Document Set. Cool Stuff!

To achieve this, at least some of us used the View settings >> Folders section options enabling us to have a second view, inside the Document Set content type.


This functionality of having 2 different views inside and outside the document sets in classic view even helped us work around the limitations of grouping in views (even now only 2 groupings are the maximum limit per view).

Interim Document Set experience

Until recently if you had document sets created in the modern view, you had that clunky experience of the modern library, opening document sets in a new tab as default.

But this enabled an opportunity to have different views for different content types, just like the classic experience. Kind of a mix of both worlds.

These were possible until recently because Document sets opened in a different tab by default (unlike the folder experience).

The latest roll out – Document set Modern experience = same as folder behavior

So when you get the latest release of modern experience for document sets, you lose out the “feature” of opening in a new tab; but instead, you get that nice experience of opening every set into the same tab, pretty seamlessly. This is very similar to a folder experience.


Problem: No more view changes based on view settings

As you may have noticed, the experience of shifting to a different view does not happen anymore.

The settings are all the same, but somehow the View settings are not taken into account.


Reading the tech community forum discussions, I was able to understand that all the modern experience settings were controlled more or less from the “Welcome Page” of the Document Set content type found in the Document Set settings.

So, to fix the view switching issue, we just have to set the “Welcome page” view to the “Document View”


And viola!


We have Document sets opening to a different view as default 🙂

Other points to note

  • Shared metadata specified in a document set content type continues to work as it always has; values inside shared columns will be copied to items inside the document set.
  • Columns that are identified as Welcome page columns in the content type are sorted to the top of the details pane so that users can find them easily. 
  • Document set versioning functionality will appear under the context menu on document set items in the modern list view, include “Capture Version” and “Version History.”
  • However, customized document set welcome pages are not supported in modern. And therefore, this change will not affect document sets that use welcome pages that have been configured with custom HTML or web parts; those welcome pages will still be displayed in classic mode, as they are today.

How to find restore option for classic SharePoint libraries in Office 365

Have you heard about the new “Restore this Library” feature for modern libraries?

It’s a really cool feature for libraries and it’s pretty straightforward to get there.

To get the Restore page in a library with modern experience

If you are in the library and click on the “gear” menu, you can easily find an extra link that says “Restore this library” – support article for the feature.


To get the Restore page in a library with the classic experience

But what if you want the same for a classic library of yours. Just add “?p=18” to the end of your library hyperlink.

In short, if your library link is:


Add the magic query string and convert that to:


Pretty easy right? 🙂