I have an idea for a UDT that will take several OPC tag connections, in combination with a couple of parameters that will enable me to create UDT’s for nearly everything in my entire project. The catch - in many cases, not all the tags that I’m declaring in my UDT will have a corresponding connection when I create the data tag(s) from the UDT. In that instance, I’ve already come up with a way to use an expression to “shunt” the OPC tag status over to an expression tag that can create a “workaround” in the event that the source OPC tag in question doesn’t connect to anything (because there won’t be anything in that instance to connect to) and returns “null” so that I can use the expression tag for things like History and Alerts trigger(s).
so my question is - what kind of negative effects will this practice have if approximately 1/2 to 2/3 of the data tags I plan to create using this method end up with at least one or possibly up to 2 (so far) OPC tags, and hence the corresponding expression tag as well (so for each one null OPC tag, 2 tags will end up labeled with that green circle with a question mark icon in the SQLTags browser), have no “real world” connection when the data tags are created? Will this condition cause problems for the system if there are ~900-1000 instances of such data tags?