I posted earlier today about using a template repeater, I switched to just using nested templates with no repeater since the repeater cannot utilize UDT’s. I have 10 nested templates in the parent template, but only 9 of them work properly. They appear to be exactly the same as far as properties and bindings. The first template that I imported doesn’t work quite right. It appears to be a problem with the template itself, as changing the tag bindings breaks the new ones. I have tried deleting and replacing the template with no success. The problem is that the timer component doesn’t write to the tag, which breaks some of the logic that runs off of that tag. The other templates which are exactly the same are able to write to tags, including the one meant for the broken template. The broken template cannot write to any of the tags. Any suggestions on something to check?
You are going to need to post some code and screen shots of the templates, bindings etc…
This is simply not true. Pass a tagpath string into your templates in dataset mode on the repeater, and use indirect binding within the template to retrieve the UDT.
Now, if you meant it cannot pass UDT properties, then you are correct. This is one of the reasons you should never use UDT properties.
Templates can only ever use UDT properties when instantiated one at a time. That templates can take UDT properties is a fundamental design flaw, for which IA staff hangs their heads in shame (sometimes takes an adult beverage or two to spur the confession). Solely to permit tag drag-n-drop in the designer.
(Fixed in Perspective, which allows tagpath-style drag-n-drop.)
ok, I had done all my property bindings by adding the UDT as a property and calling upon the tags in reference to the UDT property. Are you saying that it should be rewritten to where all variables used are individual properties rather than just calling on the UDT? That was my original plan, but it feels clunky.
Yes. Though you can indirect bind a UDT property from a tag path, you shouldn't.
Individual properties are much more efficient.
Someday, I'll identify the IA old hands who thought this was great back in the day, and feature their publicity photos in the "be honest--be honest--thank you" memes. 
I feel like this should be a sticky somewhere, and IA university needs to remove it from their tutorial.
yeah, don’t like it at all, feels super clunky, but it does work, so thank you!