UDT Parameters All Overridden In UDT instances

Hello All,

I have noticed that if I import tags tags into an 8.1.20 gateway, UDT instances have every parameter set to override. Has anyone else noticed this behavior. This is very cumbersome as they have to be manually set back to inherit from the UDT. Is there a way to prevent this or a quick fix?



Hi Frank, when creating UDT instances and setting a parameter, they should be overridden. Should every instance have the same default value for your parameter? If a UDT instance parameter was not overridden when exporting, then it should not be overridden upon importing. Please create a support ticket for this behavior so they can get a full look at the configuration.

How did you export your tags? And are you talking about just UDT parameters, or are you talking about UDT instance tag properties as well?

There's a known "issue" with the using system.tag.getConguration with system.tag.configure when you're working with UDT instance tags. The "issue" (unwanted behaviour) is that getConfiguration returns all overridden properties on tags (UDT definition non-defaults as well as UDT Instance non-defaults) instead of just the overridden properties at the UDT instance level, which is what is copied with a "Copy JSON" on the UDT Instance tag in the tag browser.
Then, using system.tag.configure with the results of getConfiguration will apply these overrides to the UDT Instance tags, effectively dis-connecting every tag in the instance from its UDT definition :confused:

1 Like