Ignition Extensions - Convenience utilities for advanced users

[nminchin]

@nminchin

I'm sure I had an idea somewhere, but my suggestion was to add an argument into the system.tag.getConfiguration function to return only the config stored on the tags themselves, not from parent settings such as non-defaults configured in the UDT definition.

This was the idea I was talking about. Is it possible to add this change into the extensions module? Or at least another function to return just the non-default config on the UDT instance and not in the definition? This is a big issue when trying to script tag changes

[FEATURE] Add option to system.tag.getConfiguration to match output of tag browser `copy JSON`

When you use system.tag.getConfiguration to get the configuration of UDt instances, it retrieves all non-default configuration of the UDT definition’s tags by deep recursively searching. If you compare this to the Tag Browser’s copy JSON functionality, this only copies the properties of the UDT definition tags that are overridden at face value, as well as of the name and tagType. When using getConfiguration with configure, the output from copy JSON is required otherwise you will essentially be…