# Ignition Extensions - Convenience utilities for advanced users

**URL:** <https://forum.inductiveautomation.com/t/ignition-extensions-convenience-utilities-for-advanced-users/64615>\
**Category:** 3rd Party Modules\
**Created:** [September 28, 2022, 6:41pm UTC](https://forum.inductiveautomation.com/t/ignition-extensions-convenience-utilities-for-advanced-users/64615 "2022-09-28T18:41:11Z")\
**Posts on this page:** 1\
**Showing post:** 32

<div class="post-metadata">

**Author:** ![nminchin](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nminchin/32/6911_2.png) [@nminchin](https://forum.inductiveautomation.com/u/nminchin)\
**Post date:** [October 19, 2022, 11:08pm UTC](https://forum.inductiveautomation.com/t/ignition-extensions-convenience-utilities-for-advanced-users/64615/32 "2022-10-19T23:08:40Z")

</div>

Is it possible to "fix" this one up as well?

> [@System.tag.configure incorrectly overriding multiple UDT tag properties](https://forum.inductiveautomation.com/t/system-tag-configure-incorrectly-overriding-multiple-udt-tag-properties/40593):
>
> I need a quick way to programmatically override properties on certain tags inside a UDT. For instance, setting a custom description for multiple iterations of the same device. The solution I’ve come up with is to read the tag configuration using system.tag.getConfiguration and then search through the result and modify the ‘value’ property for the tag in question. Then I pass the modified configuration back into system.tag.configure. I’m able to successfully change the value I want, however, …

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.

E.g. an arg to return exactly the properties that copying the JSON of a tag returns\*. Otherwise, if you use `system.tag.configure` with the results from `getConfiguration` which contains UDT instances, you end up overriding a whole bunch of properties on tags that you _ **really** _ didn't want to, that are defined in the UDT Definition! Thus essentially un-binding the UDT instances from the UDT definitions which is (hopefully) never what you want.

Ideally this fix should go into main Ignition, but for now it would be awesome to have this right now (I forgot about this `feature` yesterday and added property overrides to many many UDT instance tags which I now need to painfully remove 😕 )

\*Coincidentally, it would also be nice to have a tag context option to return what `getConfiguration` currently returns alongside the standard Copy JSON function (i.e. _return_ all of the non-defaults configured on the tag, both on the tag in the current scope as well as within its UDT definition)  
E.g.  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/1/2/127e9488dc4b5aa970ed8e606878e376e8b16006.png)

---

_[View the full topic](https://forum.inductiveautomation.com/t/ignition-extensions-convenience-utilities-for-advanced-users/64615)._