Document Set Default View

[paylord]

Is it possible to set the default view within a Document Set using PnP?

If not, can this be added as an enhancement request?

[SabbeRubbish]

Would also see the benefit to this.
e.g. via Set-PnPDocumentSetField -DefaultView

[markgort86]

For my opinion this is possible by using the following cmdlet: Set-PnPView. See also: https://pnp.github.io/powershell/cmdlets/Set-PnPView.html. There is a property for DefaultView. If you change this to true, the view will be the default.

[SabbeRubbish]

That would set the default view for the entire library/list - I think.
Not sure it would set the document set default view.

[markgort86]

Yes, it will change the default view for the whole list. But how do i reach this scenario by just using the user interface within SharePoint Online on a modern site where a document set is available? There are no view options available in the "DOCUMENT SET SETTINGS" page.

[SabbeRubbish]

In the document set settings page, at the bottom, you find the Document Set Welcome Page view:

Yes, the welcome page isn't available in Modern SharePoint, but that view is still used when you navigate to a document set in Modern SharePoint.
And this makes a lot of sense.
Say you have 6 fields in your document set like owner, start/end date, status, ... It's logical to show this in the default view for the list. However, when you click on 1 document set, all fields for all documents below it are typically synchronized with the document set, having no need to show all of those columns, hence showing a different view makes a lot of sense there.

[paylord]

Like this?

[SabbeRubbish]

Yes exactly, like my other post suggested :)

[SabbeRubbish]

Any update on this?

[crawoo]

An update on this would be great! Trying to do the very same thing now.

[SabbeRubbish]

Unfortunately, it seems like that element is the only one on that configuration page that does not have a REST counterpart.
On premises you can update the SchemaXml of the content type, but that doesn't work in SharePoint Online.

I've thought of 2 workarounds:

• Using web automation to click through the pages (see my blogpost about this)
• A though had occurred to me that we might be able to use column formatting to create the link ourselves on document sets. Probably best to do this with a SPFx customization as I think the approach with JSON may be too cumbersome (not having all necessary fields loaded in the view as just the first hurdle I see coming)