Hello
Long story short, our windows are slow to the point of unresponsiveness. Based on previous posts, we suspect one culprit might be the use of the tag() expression in our templates.
I think I've worked a way around it by using a lot of internal properties to replace the tag() expressions, but I want to be sure I won't be making things worse before we go through and redo everything 
The issue is that we created templates to be flexible enough to handle UDTs that may or may not contain all the items we want to display. So the template has multiple custom parameters for the tagpath for various inputs, and if the tagpath is blank, the template ignores by using the isgood(tag({tagpath})) logic. The only way I managed to get around that when converting to internal properties is the set the "Overlay Opt-out" checkbox on the internal properties that have indirect tags. Since sometimes the parameter is blank so the indirect tag property is in error status with no way to check isgood() since we can't use the expression within an indirect tag assignment.
Will having these errors existing but hidden, just cause new problems?
Also is there a better way than creating like 40 internal properties separately on all our templates? Could we abstract those properties to a shared dataset or something? But again, there will be a lot of properties that don't exist or don't apply to every template so I'm worried we are just moving the problem.
I was so disappointed to learn about the tag() function issues. It is super frustrating that IA provides something that makes complicated tasks easier and even teaches you how to use it without warning about the side effects. We were so proud of our smart templates that could accept all manner of tags.