# Binding to UDT parameter or UDT Instance Tag binding?

**URL:** <https://forum.inductiveautomation.com/t/binding-to-udt-parameter-or-udt-instance-tag-binding/107353>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [June 12, 2025, 10:09pm UTC](https://forum.inductiveautomation.com/t/binding-to-udt-parameter-or-udt-instance-tag-binding/107353 "2025-06-12T22:09:51Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![Anant\_Upadhyayula](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@Anant\_Upadhyayula](https://forum.inductiveautomation.com/u/Anant_Upadhyayula)\
**Post date:** [June 12, 2025, 10:09pm UTC](https://forum.inductiveautomation.com/t/binding-to-udt-parameter-or-udt-instance-tag-binding/107353/1 "2025-06-12T22:09:51Z")

</div>

I'm working with a UDT structure. In a previous project, I developed a tank template using parameterized UDT instances to display tag values dynamically based on the Tank Number. That implementation was read-only—no operator interaction was required.

For displaying values, I used property bindings such as:  
`view.params.BTankUDT.Current.Material_No`

In my current project, I need to design a dashboard UI where operator input and control are required. Given this shift from a passive display to active interaction, should I continue with direct tag bindings as before, or implement indirect bi-directional tag bindings to allow for dynamic writes to the underlying UDT tags?

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [June 12, 2025, 10:46pm UTC](https://forum.inductiveautomation.com/t/binding-to-udt-parameter-or-udt-instance-tag-binding/107353/2 "2025-06-12T22:46:26Z")

</div>

Bind only the UDT path, use indirect bindings to tags under this path for all items in the template.

---

<div class="post-metadata">

**Author:** ![michaeelphillips](https://avatars.discourse-cdn.com/v4/letter/m/cc9497/32.png) [@michaeelphillips](https://forum.inductiveautomation.com/u/michaeelphillips)\
**Post date:** [June 13, 2025, 12:13am UTC](https://forum.inductiveautomation.com/t/binding-to-udt-parameter-or-udt-instance-tag-binding/107353/3 "2025-06-13T00:13:29Z")

</div>

Thanks for the clarification, David. Just to confirm, when you say "bind only the UDT path," you're referring to setting that as a custom property on the view or component and then using indirect bindings (e.g., `{custom.udtPath}/Current/Material_No`) for individual tag values within the template, correct? That seems like a clean way to handle both read and write operations without hardcoding specific paths.

Appreciate the insight, just making sure I'm understanding the recommended approach correctly.

---

<div class="post-metadata">

**Author:** ![Anant\_Upadhyayula](https://avatars.discourse-cdn.com/v4/letter/a/e36b37/32.png) [@Anant\_Upadhyayula](https://forum.inductiveautomation.com/u/Anant_Upadhyayula)\
**Post date:** [June 13, 2025, 2:12am UTC](https://forum.inductiveautomation.com/t/binding-to-udt-parameter-or-udt-instance-tag-binding/107353/4 "2025-06-13T02:12:48Z")

</div>

@David_Stone Thank you for sharing the insight. If possible can you please show an example or confirm what @michaeelphillips wrote.

---

<div class="post-metadata">

**Author:** ![David\_Stone](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/david_stone/32/79749_2.png) [@David\_Stone](https://forum.inductiveautomation.com/u/David_Stone)\
**Post date:** [June 13, 2025, 2:16am UTC](https://forum.inductiveautomation.com/t/binding-to-udt-parameter-or-udt-instance-tag-binding/107353/5 "2025-06-13T02:16:40Z")

</div>

This is exactly what I mean, this means that only one item changes when changing the UDT pointed to, and also this gives you the ability to do some other tricks:

- Write to tags with indirect references
- Bind to parameters and metadata like "EngUnit" of individual tags in the UDT.