# Alarm Metrics not bindable in templates?

**URL:** <https://forum.inductiveautomation.com/t/alarm-metrics-not-bindable-in-templates/114063>\
**Category:** Ignition\
**Tags:** ignition83, vision\
**Created:** [February 19, 2026, 12:59pm UTC](https://forum.inductiveautomation.com/t/alarm-metrics-not-bindable-in-templates/114063 "2026-02-19T12:59:00Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Greyship](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Greyship](https://forum.inductiveautomation.com/u/Greyship)\
**Post date:** [February 19, 2026, 12:59pm UTC](https://forum.inductiveautomation.com/t/alarm-metrics-not-bindable-in-templates/114063/1 "2026-02-19T12:59:00Z")

</div>

8.3.4 RC 1, I created a UDT for a Valve object, and that UDT has a very helpful Alarm Metrics folder.

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/c/8cd0b7b80311dd3a646560347422719f9f3e3114.png)

But when using the UDT as a parameter property to a template, none of the alarm metrics appear as bindable properties of the UDT:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/2/72a5d196bb32d239d54c11c916092870cf6d3a2a.png)

(Meta is a folder in the UDT that I created) Is this by design, or a bug?

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [February 19, 2026, 2:19pm UTC](https://forum.inductiveautomation.com/t/alarm-metrics-not-bindable-in-templates/114063/2 "2026-02-19T14:19:31Z")

</div>

> [@Greyship](#):
>
> UDT as a parameter property to a template

Stop. Don't use UDT parameter properties. (Like, ever. Lots of forum discussions on why.)

Use a string tagpath property. Use indirect binding everywhere within the template that needs live data, and concatenate the tagpath parameter with the trailing names.

---

<div class="post-metadata">

**Author:** ![Greyship](https://avatars.discourse-cdn.com/v4/letter/g/898d66/32.png) [@Greyship](https://forum.inductiveautomation.com/u/Greyship)\
**Post date:** [February 19, 2026, 3:56pm UTC](https://forum.inductiveautomation.com/t/alarm-metrics-not-bindable-in-templates/114063/3 "2026-02-19T15:56:02Z")

</div>

Thanks again Phil, I changed to indirect tags and this seems to work now.

---

<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:** [February 20, 2026, 7:52am UTC](https://forum.inductiveautomation.com/t/alarm-metrics-not-bindable-in-templates/114063/4 "2026-02-20T07:52:40Z")

</div>

It's kind of ironic; the reason they're not included in the return from a UDT type parameter is very likely one of the biggest reasons we all highly recommend against using UDT Type params altogether, and that is performance impact due to the number of tag subscriptions that might be created. Add to that also the large number of alarm metrics tags, and it would have even more of a performance impact