In one of the updates to 8.0 or 8.1 the properties for alarm info on a tag changed. Thats kind of understandable, but the worst change was that Alarms.HighestUnackedPriority now is supposed to be an integer, but instead of being an integer value when there are no alarms, it evaluates to null. Couldn't 0 or -1 be used instead of null? in an expression, the null value has to be caught like an exception, and it would be nice to just have a -1 there.


Consider using coalesce() instead of try().

That is better than what I was doing.