# Strange Alarm Setpoint Binding Dicsovered

**URL:** <https://forum.inductiveautomation.com/t/strange-alarm-setpoint-binding-dicsovered/27733>\
**Category:** Ignition\
**Tags:** ignition80\
**Created:** [August 23, 2019, 8:39pm UTC](https://forum.inductiveautomation.com/t/strange-alarm-setpoint-binding-dicsovered/27733 "2019-08-23T20:39:41Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![brandon1](https://avatars.discourse-cdn.com/v4/letter/b/ea666f/32.png) [@brandon1](https://forum.inductiveautomation.com/u/brandon1)\
**Post date:** [August 23, 2019, 8:39pm UTC](https://forum.inductiveautomation.com/t/strange-alarm-setpoint-binding-dicsovered/27733/1 "2019-08-23T20:39:41Z")

</div>

I have been trying to update the methods used to grab alarm setpoints configured on tags and found this strange ‘bug’.

I want to run this by developers to see if I should be using this or if it is going to break on the next update.

I am setting up indirection to go to the following path:  
{1}/Alarms/High.setpointA  
The referenced variable is simply a string representing the path to the tag. I have confirmed that this does update when the value of the configured alarm changes.

Please advise if I need to come up with a different method as this property is not actually listed on the Tag Browser.

Thanks,