Forum Discussion
Updating content type templates on 9000 libraries...
Hi everyone - I wanted to see if any of you have experienced the issue that I am currently faced with, and if you have any suggestions for how I can get out of the difficulty that we're in! We ha...
Which version of SP are you working with and can you describe how you are doing this update? Do the templates include document properties?
In modern SP there are two ways of using document templates:
- by configuring the content type through the content type advanced settings (the "classic" way). This connects a template to a specific content type.
- by uploading templates to the library (the "modern" way). This way you can select whatever template you want and then define the content type when editing the document properties.
Maggan Wåhlin Thanks very much for coming back to me 🙂
This is using modern team sites in SharePoint Online. When we originally configured it, we had a series of content types, each with properties associated (mostly connecting to Managed Metadata sources). Each content type had a document template applied to it (through the advanced settings of the CT, and uploading a file). The issue now is, because of the volume of libraries in there, if I try and replace that document template in the content type, it just hangs on "Working on it". I noticed that SharePoint copies this template to each library, so when replacing it, it first has to delete it everywhere, and then replace it with the new one, and this is where we have the problem. SharePoint seems to treat this like some kind of DoS potential, and hangs on it.
Any thoughts?
Thanks again
Alex
I agree that it probably has to do with the large volume doc libs...
Maybe PowerShell could help you? Found an article on this here: https://simondoy.com/2016/05/24/powershell-update-sharepoint-content-type-document-template-script/
We thought that too, and tried it using Powershell. The problem is that when it tries to push this out to 9000 libraries, SharePoint then blocks it, and waits between each operation (because of the large amount of activity it's a potential performance threat). Each time it doubles the amount of time it waits, which is then an ever-increasing number. Last time I gave up after running the update for 36 hours straight 😞
