# Relative Tag Path and Alarm Priority

**URL:** <https://forum.inductiveautomation.com/t/relative-tag-path-and-alarm-priority/104612>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [April 2, 2025, 9:00pm UTC](https://forum.inductiveautomation.com/t/relative-tag-path-and-alarm-priority/104612 "2025-04-02T21:00:01Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Molson](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Molson](https://forum.inductiveautomation.com/u/Molson)\
**Post date:** [April 2, 2025, 9:00pm UTC](https://forum.inductiveautomation.com/t/relative-tag-path-and-alarm-priority/104612/1 "2025-04-02T21:00:01Z")

</div>

I am attempting to condition(using an expression) the priority of a UDT instance's alarm priority based on the value of another tag.

Below is the rough structure of that alarm priority value I'm trying to set, and the OPCTag value I need to reference,  
[TagProvider]A/ **B** /N/UDTInstance\_ **B** /AlarmFolder/OPCTag/Alarms/Alarm.Priority

[TagProvider]A/ **B** /C/DifferentUDTInstance\_ **B** /AlarmFolder/OPCTag

I need to make this binding generic enough such that **B** can change and my expression will still work, but I'm not sure how to make this work since I can't declare " **B**" as a variable using expression syntax. In my project, **B** is a folder representing a process #, and is used as the suffix for instances of UDTs of which there are many.

Does anyone have any ideas how I might be able to solve this? I've tried using scripting, but it seems ignition blocks writing to the .priority property.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [April 2, 2025, 9:35pm UTC](https://forum.inductiveautomation.com/t/relative-tag-path-and-alarm-priority/104612/2 "2025-04-02T21:35:49Z")

</div>

Your script might need to write to a parameter of the UDT instance which has the alarm configured, which can be referenced in the binding for the alarm severity.  
I’m not a huge fan of writing to params across separate UDT instances, so leave bread crumbs (document the process) for the person who has to reverse engineer / troubleshoot any issues.

---

<div class="post-metadata">

**Author:** ![Molson](https://avatars.discourse-cdn.com/v4/letter/m/e0b2c6/32.png) [@Molson](https://forum.inductiveautomation.com/u/Molson)\
**Post date:** [April 2, 2025, 9:42pm UTC](https://forum.inductiveautomation.com/t/relative-tag-path-and-alarm-priority/104612/3 "2025-04-02T21:42:55Z")

</div>

Thanks, I was hoping to avoid adding another parameter or property if possible. Preferentially using an expression, however it's turning out to be more complicated than I expected.

---

<div class="post-metadata">

**Author:** ![Chris\_Bingham](https://avatars.discourse-cdn.com/v4/letter/c/e5b9ba/32.png) [@Chris\_Bingham](https://forum.inductiveautomation.com/u/Chris_Bingham)\
**Post date:** [April 2, 2025, 10:31pm UTC](https://forum.inductiveautomation.com/t/relative-tag-path-and-alarm-priority/104612/4 "2025-04-02T22:31:12Z")

</div>

You could set up two (or more) separate expression tags (with static alarms configured on each) whereby only one would turn on based on status of other tag values.