# Access UDT parameter in script

**URL:** <https://forum.inductiveautomation.com/t/access-udt-parameter-in-script/27824>\
**Category:** Ignition\
**Created:** [August 28, 2019, 7:55am UTC](https://forum.inductiveautomation.com/t/access-udt-parameter-in-script/27824 "2019-08-28T07:55:45Z")\
**Posts on this page:** 1\
**Showing post:** 26

<div class="post-metadata">

**Author:** ![tyler.bennett](https://avatars.discourse-cdn.com/v4/letter/t/f04885/32.png) [@tyler.bennett](https://forum.inductiveautomation.com/u/tyler.bennett)\
**Post date:** [December 20, 2023, 11:42pm UTC](https://forum.inductiveautomation.com/t/access-udt-parameter-in-script/27824/26 "2023-12-20T23:42:33Z")

</div>

I rediscovered this bug/behavior today in v8.1.35. Cross-posting here as it has some relevance. It seems Ignition attempts parameter resolution even on commented lines and will fail silently if there is something in curly brackets that is not a valid parameter.

> [@\[Bug Report\] Curly brackets (braces) on commented line in udt instance script causes script to fail silently](https://forum.inductiveautomation.com/t/bug-report-curly-brackets-braces-on-commented-line-in-udt-instance-script-causes-script-to-fail-silently/79124):
>
> Including open/close curly brackets (braces) with any text in between, on a commented line (e.g. #{z}), in a value changed value event script, on a tag in a udt definition... causes the script to fail silently on UDT instances showing no errors in the script editor and no errors in the logs. Any of these lines causes silent failure of the script with no lines executed. #{L} # here is an innocuous comment that should not affect anything but {does} I tested for the same on atomic tags not in a…

---

_[View the full topic](https://forum.inductiveautomation.com/t/access-udt-parameter-in-script/27824)._