If you create your templates from files using good ol' fashioned pre-SharePoint storage (hard disk ;) ) and upload them using the "upload a new document template" option along with the content type, then you will get the desired results.

Hmm, I'm waiting for Microsoft to try and convince me now that this is a "know issue by design". It's a clear bug. Once SharePoint has added a customxml folder and associated files into the docx package you're pretty much screwed. This also puts the end to any ideas of using a standards library as the basis for all the content types used within the business. Also - try getting your quickparts spot on if you can't ever put the template in the library to get the quickparts list populated...
The workaround suggested elsewhere - upload documents only, don't create from new - is pretty lame I think. Let's see what Microsoft have to say...
Hi Paul, did you find a solution to this with Microsoft? I am seeing the same issues in one of my sites. Any ideas for a workaround?
ReplyDeleteI came acros this fix which works!! Thanks to the authors!
ReplyDeleteProblem Solved: Amnesia Problem: Multiple Content Types on Libraries