The Detail Template file is already associated with the Preference Set.
However, the filename itself can vary between installations. We opted for a more simplistic file naming, of just DETL-001, incremented up for each preference set installed.
Which just means that after merging preference sets into your one cloud-based installation, it will require some template file cleanup.
The steps would be as I noted previously -- from a blank drawing, cycle through each preference set, and open each template, logging the filename opened for each.
You can then rename/copy/replace as necessary.
It is certainly an intriguing idea to have the template co-located with the detail library. However it seems some users may wish to have multiple preference sets accessing the same detail library, yet using different template files. So the need will still be there to have differently named template files. I think the method we have is still preferable to the other possibilities, of deriving from the preference set name, or using a random key number.
Note that there is a little hidden fix in there -- you can delete all template files from the folder, and leave just DETL-000, which will get copied as necessary for use by all preference sets.
--J