Add CSOM support for Document Set settings on content type
Please consider adding support for setting/retrieving doucment set properties on a content type. We need to be able to set properties like Shared columns, Welcome page and Welcome page view on the document set.
Nicolaj Hedeager Larsen
shared this idea
Thanks for your feedback! Although we appreciate your time and effort to give us this feedback, it’s not something we’re planning to do right now.
We are not evolving the CSOM API surface as such, but would recommend on checking possibility to use Graph API for this scenario at https://docs.microsoft.com/en-us/graph/api/resources/contenttype?view=graph-rest-beta
6 comments
Comments are closed-
Alberto Suarez
commented
I know, I ended creating a spfx extension to control the doc set view and add a kind of "docset welcome page"...another hack. However, who knows when a MS solution for this will take a place, and I had the need to deliver a solution for the customer.
On the other hand, just fyi, even if you customize the documentset default view, applying later changes to library by pnp templates will reset such value to the same viewid that library has as default.
Good luck ;)
-
Ruslan Urban
commented
Thank you @Alberto. I saw the headless IE implementation, but this is rather a hack thank a solution...
-
Alberto Suarez
commented
There is no solution for this so far, however, you can perform this configuration with powershell or typescript, and some headless browser library, or the IE from powershell.
Then, you will progam click here and here in order to change the default view for the docset ;) -
Ruslan Urban
commented
Any idea if this request has even been considered to be addressed? There is no way to set Document Set Welcome Page View ID remotely. There is no support for it in CSOM or REST. I needed this functionality to implement provisioning of document libraries with extensive use of document sets for a few clients, but my hands are tied. Which also means that now the client need to engage support every time they create a new site to update the document set welcome page view manually. One client in particular is expecting to create over 1000 sites with the number of document libraries ranging from 11 to over 50 per site. Most of them utilize document sets to implement records management classifications. Hope, Microsoft can address this issue in timely manner and analyze the current state of document sets functionality in general - there are a few issues with the current implementation. I can provide with some details.
-
Anonymous
commented
CSOM has been around for eight years now (frameworks have been born and died in that amount of time), and we have still whole feature blocks that we can throw away when developing using CSOM. C'mon Microsoft, add a few more endpoints please, can't be too much work! :)
-
Pauli Visuri
commented
The inability to set the Welcome page view means that at the moment Document Sets are practically useless. The way that Sets are normally used is that the Set has fields and properties which enable the user to choose the right Set, before navigating into it - these are shown in the library's default view. The document content types will then have (at least partially) different fields and properties, for the user to identify the correct document; these should be shown in the set's Welcome view. But at the moment when the Set content type is created using the API, it will use the library's Default View and we are unable to set any other view! At the moment this means that we have to add ALL fields (those for the Set and those for the Document types) in the default view, but this makes for a poor user experience as the user will be presented with lots of fields which are not relevant (and typically blank) in the location where they are.
There is a further "bug" as well: I attempted working around this by creating 2 "location views" - i.e. one specifying in View Settings that it should apply to (and be defaullt in) library root, and in another that it should apply to the Set content type. However, the result was that the Set welcome page was not rendered at all, and the Set ribbon tab did not appear; SharePoint displayed the Set as an ordinary folder.
