I’m trying to build a pen tag path in script to pass it to a new window with an Easy Chart on it. I can do this from within a template where the tag is a UDT tag. From this I can get the tag path from the UDT “Meta.TagPath” property and use it to substitute the tag provider with the tag history provider. This provides a string that can be passed to the easy chart tag pens dataset.
I want to do this for a single atomic tag as well but I cannot find any access to the tag path in properties or in script. There is nothing like the “Meta.TagPath” for an atomic tag and I cannot find any other way to do this dynamically (without knowing the name and tag path of the tag) in script.
I know what you are saying - I’ve heard you (and others) say this before. The problem is that the template needs a number of tags that just make it easier to do with a UDT tag. The UDT is not large, but it is all-encompassing for the template. And the template using the UDT works fine. The template with the atomic tag only uses one custom property for the tag, but now I have to add another custom property (besides the tag itself) in order to have the path? If I can right click on the tag and copy the tag path, why is it not available in scripting?
I keep hearing IA personnel say not to use UDTs, but then why are they part of the system? Of course the UDT works fine so this is really not part of this discussion in my opinion.
I honestly just wish they’d remove the option to define a custom prop with a UDT type (or at least disable the option in gateway config). I’m not aware of a use case where the UDT prop provides any benefit over using a path to the UDT instance instead.
In any case, @tbennett.tdc as the others have already stated DO NOT use UDT props as parameters. The parameter should be the string path to the UDT instance. Then define internal props for each tag you need and indirectly bind to those internal props and bind anything in your UI to those internal props.