# Access UDT root custom property inside a Tag Expression

**URL:** <https://forum.inductiveautomation.com/t/access-udt-root-custom-property-inside-a-tag-expression/115361>\
**Category:** Ignition\
**Created:** [May 3, 2026, 7:15am UTC](https://forum.inductiveautomation.com/t/access-udt-root-custom-property-inside-a-tag-expression/115361 "2026-05-03T07:15:36Z")\
**Posts on this page:** 1\
**Page:** 2

<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:** [May 24, 2026, 3:45pm UTC](https://forum.inductiveautomation.com/t/access-udt-root-custom-property-inside-a-tag-expression/115361/22 "2026-05-24T15:45:17Z")

</div>

The use of `tag()` is not discouraged in expression tags. There's no alternative, as there's no such thing as indirect binding otherwise.

The `tag()` function has pathological startup behavior that is especially troublesome in UI bindings, plus it has to completely re-execute its string expression on every tag update, which imposes extra CPU load compared to indirect bindings.

Finally, when you have multiple `tag()` expressions or tag bindings contributing to an expression, they are all independently asynchronous, and will trigger expression re-execution independently. The batching time argument to my `tags()` expression function specifically addresses this troublesome behavior.

[Previous page](https://forum.inductiveautomation.com/t/access-udt-root-custom-property-inside-a-tag-expression/115361.md?page=1)
