# Accessing UDT parameters does not allways work

**URL:** <https://forum.inductiveautomation.com/t/accessing-udt-parameters-does-not-allways-work/9127>\
**Category:** Ignition\
**Created:** [October 1, 2014, 1:54pm UTC](https://forum.inductiveautomation.com/t/accessing-udt-parameters-does-not-allways-work/9127 "2014-10-01T13:54:44Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![mik977](https://avatars.discourse-cdn.com/v4/letter/m/5f8ce5/32.png) [@mik977](https://forum.inductiveautomation.com/u/mik977)\
**Post date:** [October 1, 2014, 1:54pm UTC](https://forum.inductiveautomation.com/t/accessing-udt-parameters-does-not-allways-work/9127/1 "2014-10-01T13:54:44Z")

</div>

I made an UDT. Inside I put some OPC tags. One of this tags has an alarm associated. Within this alarm I made 2 associated data params, Text1 and Text2. I then added an expresson binding to both of them so they would reference UDT properties of the same name, Text1 and Text2, which I also created in the UDT.

After configuring the UDT I made an instance of it and assigned some text to the params Text1 and Text2. The bindings are obviously not working because I have an error overlay on the tag. When I inspect the tag in the Tag Diagnostics Dialog, the errors for both alarm associated properties say:

Syntax error on token: ‘End of expression’ (Line 0, Char 0)

The expression I use on both associated Data properties Text1 and Text2 are {Text1}, {Text2} respectively.

So, my question is: am I doing something wrong or expression bindings in this case are not working properly?

Using: Ignition 7.7.1

---

<div class="post-metadata">

**Author:** ![matt.eaton](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/matt.eaton/32/72046_2.png) [@matt.eaton](https://forum.inductiveautomation.com/u/matt.eaton)\
**Post date:** [October 9, 2014, 11:59pm UTC](https://forum.inductiveautomation.com/t/accessing-udt-parameters-does-not-allways-work/9127/2 "2014-10-09T23:59:54Z")

</div>

I’ve noticed some weirdness with parameters in alarms.  
[https://www.inductiveautomation.com/forum/viewtopic.php?f=72&t=12646](https://www.inductiveautomation.com/forum/viewtopic.php?f=72&t=12646)

I suggest putting “{Text1}” in the expression to see if that works.