add to schema Functionality to set Document set view

[KbWorks]

It would be nice to have the possibility to add a view to a document set per listinstance.

pnp:Documentset
<pnp:contenttype id="" name="">
<pnp:view name="all documents"></pnp:view>
pnp:contenttype
</pnp:Documentset>

[PaoloPia]

Hi,
Thanks for your feedback. The idea is great, and someone else already submitted it, too. However, we need to figure out how to implement this capability at the engine level.

[KbWorks]

Hi Paolo,

thank you i wrote a extension method for it maybe you can use it in the core in combination with the schema change.

[PaoloPia]

Hi Paul,
Sorry for the delayed answer, where is the extension method? Is it in Core or in your own code somewhere else? Can you share it? Thanks.

[KbWorks]

Hi Paolo,

will look it up and send a message thanks again.

Paul

[KbWorks]

Hi Paulo,

have not tested if it still works but i can test it if you want.
` ///

/// sets the view for a Documentset welcome page.
///

/// The context.
/// The web.
/// The list.
/// The contenttype.
/// The contenttype.
private void SetDocumentSetView(ClientContext context, Web web, List spList, string pContentType, string welcomePageview)
{

        //var contenttype = spList.ContentTypes.GetById(pContentType);
        context.Load(spList, l => l.ContentTypes);
        context.ExecuteQuery();

        var contenttype = spList.ContentTypes.FirstOrDefault(c => c.Name == pContentType);
        var viewid = spList.GetViewByName(welcomePageview).Id;

        var docSetTemplate = DocumentSetTemplate.GetDocumentSetTemplate(context, contenttype);

        //context.Load(contenttype, c => c.SchemaXmlWithResourceTokens);
        context.Load(contenttype, c => c.SchemaXml, c => c.SchemaXmlWithResourceTokens);
        context.Load(docSetTemplate);
        context.ExecuteQuery();

        var xmlschema = string.IsNullOrEmpty(contenttype.SchemaXmlWithResourceTokens) ? contenttype.SchemaXml : contenttype.SchemaXmlWithResourceTokens;
        if (xmlschema.Contains("XmlDocuments"))
        {
            XmlDocument xmldocument = new XmlDocument();
            xmldocument.LoadXml(xmlschema);

            XmlNodeList xmldocs = xmldocument.SelectNodes("ContentType/XmlDocuments/XmlDocument");
            foreach (XmlNode xmldoc in xmldocs)
            {
                if (xmldoc.ChildNodes.Count > 0)
                {                    
                    var firstChildNodeName = xmldoc.FirstChild.Name;    //xmldoc.ChildNodes[0].Name;
                    if (firstChildNodeName == "WelcomePageView")
                    {
                        // Create new default view XML
                        string newDefaultViewXml = string.Format(@"<wpv:WelcomePageView xmlns:wpv='http://schemas.microsoft.com/office/documentsets/welcomepageview' ViewId='{0}' />", viewid);

                        // Replace default view XML
                        xmldoc.FirstChild.InnerXml = newDefaultViewXml;

                        // Exit foreach loop
                        break;
                    }
                }
            }

            StringWriter sw = new StringWriter();
            XmlTextWriter tx = new XmlTextWriter(sw);
            xmldocument.WriteTo(tx);
            xmlschema = sw.ToString();

             contenttype.Update(false);
           
        }
    }`

[PaoloPia]

Hi @KbWorks,
We just added to the upcoming new schema version a XmlDocuments element for the DocumentSet. In the future, we will add corresponding functionality at the engine level. Thanks.

[rajajii]

Hi KbWorks
Most likly your code is for SharePoint onpremises. I tried your approach on sharepoint online, but it did not work since SchemaXml is readonly property in online version.

Thanks anyway

[frankok]

Hi @PaoloPia,
Is this now added and supported in 2018/07 schema, or has it just been added for future use?

[holylander]

Hi @PaoloPia ,

I am trying to define the default view for a docset using this code
<pnp:XmlDocuments> <pnp:XmlDocument NamespaceURI="http://schemas.microsoft.com/office/documentsets/welcomepageview"> <pnp:WelcomePageView xmlns="http://schemas.microsoft.com/office/documentsets/welcomepageview" ViewId="539D3C0D-D299-494F-AC5D-DF603B0FFDB1" /> </pnp:XmlDocument> </pnp:XmlDocuments>
but It doesnt work. Any suggestion idea how to fulfill this? thanks!!

[holylander]

Hi KbWorks
Most likly your code is for SharePoint onpremises. I tried your approach on sharepoint online, but it did not work since SchemaXml is readonly property in online version.

Thanks anyway

I can confirm the previous statement.
It seems there is not any way to implement this on sharepoint online so far
https://sharepoint.stackexchange.com/questions/256463/pnp-provisioning-welcomepageview-in-document-sets

On the other hand, if you are on premises you can change the documentset welcomepageview

[poidah]

So here we are 5 years later and there doesn't seem to be a programatic or declaritive way to set the view to be used within a document set.

One would assume this would have to be a setting at the library level - this is because:

• There are no views defined at a site level (along with site columns and site content types)
• The library and the view need to exist for there to be a ViewID to reference

Please Microsoft, how do we use your tools in a scalable way?

[T-LeGranc]

So here we are 2 more years later and this is still not possible.

[MrRCG5]

Can we update the "ViewId" in the "SchemaXML"? I tried and the SchemaXML is read-only.

[zenlord]

@MrRCG5 Yes, that's the way to do it currently, and it is pretty easy:

$welcomePageView = Get-PnPView -Identity $view.Displayname -List $list
$xml = [xml](Get-PnPContentType -Identity $ctType.Name -List $library | Select -Expand SchemaXml)
$node = $xml.ContentType.XmlDocuments.XmlDocument | where {$_.NamespaceURI -eq 'http://schemas.microsoft.com/office/documentsets/welcomepageview'}
$node.InnerXml = "<wpv:WelcomePageView xmlns:wpv=`"http://schemas.microsoft.com/office/documentsets/welcomepageview`" ViewId=`"$($welcomePageView.Id)`" />"

[MrRCG5]

newDefaultViewXml

It is not working for me using SharePoint online. How is "$node.InnerXml" being updated? Do I need to execute or invoke a change?