# Reading and Writing Tag's UDT Parameters

**URL:** <https://forum.inductiveautomation.com/t/reading-and-writing-tags-udt-parameters/67745>\
**Category:** Ignition\
**Created:** [December 16, 2022, 10:30pm UTC](https://forum.inductiveautomation.com/t/reading-and-writing-tags-udt-parameters/67745 "2022-12-16T22:30:19Z")\
**Posts on this page:** 1\
**Showing post:** 7

<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:** [December 20, 2022, 8:48pm UTC](https://forum.inductiveautomation.com/t/reading-and-writing-tags-udt-parameters/67745/7 "2022-12-20T20:48:42Z")

</div>

Take care with using configure with getConfiguration though. Search the forum for posts by me on the subject

Eg

> [@\[FEATURE\] Add option to system.tag.getConfiguration to match output of tag browser \`copy JSON\`](https://forum.inductiveautomation.com/t/feature-add-option-to-system-tag-getconfiguration-to-match-output-of-tag-browser-copy-json/62807):
>
> 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…

---

_[View the full topic](https://forum.inductiveautomation.com/t/reading-and-writing-tags-udt-parameters/67745)._