# UDT Tag Browser awareness

**URL:** <https://forum.inductiveautomation.com/t/udt-tag-browser-awareness/104200>\
**Category:** Ignition\
**Tags:** vision\
**Created:** [March 25, 2025, 9:23pm UTC](https://forum.inductiveautomation.com/t/udt-tag-browser-awareness/104200 "2025-03-25T21:23:56Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![sherman](https://avatars.discourse-cdn.com/v4/letter/s/e5b9ba/32.png) [@sherman](https://forum.inductiveautomation.com/u/sherman)\
**Post date:** [March 25, 2025, 9:23pm UTC](https://forum.inductiveautomation.com/t/udt-tag-browser-awareness/104200/1 "2025-03-25T21:23:56Z")

</div>

Is there a way to make a UDT aware of its own tag provider? I am still trying to figure out how to build a switch at as high of a level in a tag provider as possible to allow tags inside that provider to reference specific paths in other providers "indirectly", and I was considering doing things like tag providers named like `[HMI-myProject]` so that I can scrape myProject out of the tag provider name and have "project aware" tags that have that information actually exist at gateway level.

When I use {PathToTag} inside the UDT in an expression, it **does not** contain the tag provider name, best I can get is [.] and [~], and I want to remove those shortcuts and go by absolute path instead of these relative paths. Effectively I want something that does `substring(split({PathToTag}, "]"), 0), 1)` but actually works. A "get\_tag\_provider()" type method, if you will.

I really really just want "indirect" tags for reference much how there are indirect tags in the property bindings for Vision, but at the core data level.