Allow Document Template URL within Content Type Hub
Content Types created within the Content Type Hub allow for the addition or a Document Template via URL. However, when these are published to alternate Site Collections they will not work due to the URL being Relative to the Site Collection that they are published to. (Confirmed by MS Support Team)
This means that updating a Document Template requires administrators to re-upload the document to the Content Type as opposed to having the changes replicated automatically that would be expected in a properly managed Document Control System.
Please allow URL Templates to work correctly for the Content Type Hub.
Ryan Robinson commented
This is a weird thing to not work. I eventually figured out that I needed to use a relative URL to get the Content Type Gallery to accept my template. But then I go to test it on a library and it just opens a blank tab. No error to help sort out what's wrong or anything, had to go digging on support forums.
I don't get why it would be a problem to accept an absolute URL.
David Buckley commented
Funnily enough I was looking for a resolution to this issue and found that this post was posted by my companies Senior SharePoint consultant in 2017! I thought I would share a work around I found, even if still not ideal, sorry if its already been posted. If you default the library where the content types are added to 'Open in Client Application', the templates will load fine from the content type hub. This means you can still have a central location where the templates are stored, preventing manual upload on each library, but it does mean that the files will always open in the desktop application. I cannot believe that Microsoft haven't resolved this issue in all this time when in reality it would appear to be a pretty simple to fix bug.
Another absolutely attrocious oversight! The fact 5+ years on its still an issue is flabbergasting. When templates are uploaded into a content type, direct access to them is not possible anymore, allot of the time they cannot be cleaned up and in effect they sit in in a tenant admin invisible library with the only means to update the content is to upload on top of the existing template. Multiply this x 100 documents and this is an absolute nightmare. Why the actual document constituting the template cannot be placed into the Hub or the Content Type library for a site collection to distribute downstream and also be able to update in one location is beyond me. Were the dev's sniffing the white stuff when some of those decisions were made? Annoying as ****!!!
SHANAKA NARANPANAWE commented
Very disappointed that this is not yet possible. MS pushes us to go in this flaten site structure which means that the CTH plays a vital role in terms of getting columns and content types to be available through out a solution and these options are very important in terms of usability of these features.
I find it crazy and ridiculous that this is not already an option. I started using the Content Type Hub as we move to the Modern sites specifically due to the fact that I could have our forms stored in a quality site and be managed with approval requirements and version control, and then linked to the content type. not allowing it defeats the purpose of the content types and the ability to add a link to the document in the library it belongs in. Here it is 3 years later and this is still not an option. HOW???
This seems like it should be a logical request and would be best practice. If required you could override the template on the individual site collection. This should be put in asap and should be quite simple to do.
Carry Megens commented
URLs are specified as /sites/... but fail. Please make this work. If templates are inside a contentType hub lib that is already better than having to upload each change in template.