# Runtime Tag Alarm Properties Changes in 8.0? -1 vs. Null?

**URL:** <https://forum.inductiveautomation.com/t/runtime-tag-alarm-properties-changes-in-8-0-1-vs-null/35701>\
**Category:** Ignition\
**Created:** [June 16, 2020, 1:46pm UTC](https://forum.inductiveautomation.com/t/runtime-tag-alarm-properties-changes-in-8-0-1-vs-null/35701 "2020-06-16T13:46:03Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![cezipper](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@cezipper](https://forum.inductiveautomation.com/u/cezipper)\
**Post date:** [June 16, 2020, 1:46pm UTC](https://forum.inductiveautomation.com/t/runtime-tag-alarm-properties-changes-in-8-0-1-vs-null/35701/1 "2020-06-16T13:46:03Z")

</div>

I recently upgraded from 7.9 to 8.0. It looks like there have been changes to the runtime tag alarm properites (7.9 had “.AlarmHighestUnackPriority” and 8.0 seams to have it as “/Alarms.HighestUnackPriority”) but I also see that 7.9 used to have a value of -1 when there was no unacked alarms. my tag browser is shown nothing. I don’t know if that is an empty string or null or what. I had a lot of logic that used 7.9’s -1 value. Can someone confirm what the no acked alarms value is, or point me to documentation that explains it? If -1 has been replaced with something else, can you point me to some guidelines on how to use that something else in scripting and expressions? For example, I used to be able to check if that value was \> 1, but now what results if null is checked for \>1?

Here is a clip of the 7.9 structure from a InductiveU vedio  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/d/dbe0d581f7356365e2ed62ab51a699135f128442.png)

Here is a clip from my 8.0 tag browser with the null or empty value:

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/2X/3/32f389ae29fd40fda204937558d856cb39f5ed7e.png)

---

<div class="post-metadata">

**Author:** ![jonathan.taylor](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jonathan.taylor/32/4048_2.png) [@jonathan.taylor](https://forum.inductiveautomation.com/u/jonathan.taylor)\
**Post date:** [June 16, 2020, 3:41pm UTC](https://forum.inductiveautomation.com/t/runtime-tag-alarm-properties-changes-in-8-0-1-vs-null/35701/2 "2020-06-16T15:41:23Z")

</div>

Have you tried

> if value is not None

---

<div class="post-metadata">

**Author:** ![cezipper](https://avatars.discourse-cdn.com/v4/letter/c/58956e/32.png) [@cezipper](https://forum.inductiveautomation.com/u/cezipper)\
**Post date:** [June 16, 2020, 4:00pm UTC](https://forum.inductiveautomation.com/t/runtime-tag-alarm-properties-changes-in-8-0-1-vs-null/35701/3 "2020-06-16T16:00:29Z")

</div>

I am sorry I was not more direct on my main concern. I have not tried anything yet because my 7.9 project has a lot of logic that uses the -1 value that used to be there. I want to make sure the null is the norm now before I put work into that. I have had other tag values go to null when I was not expecting it and I can not find any documentation that says what the value should be if there are no alarms. I guess I should have tested the system by cycling through alarm states and see what value it takes (seeing if it consistently goes to null or -1). I will do that.