# Perspective Alarm Status Table & Event Value column scaling/formatting

**URL:** <https://forum.inductiveautomation.com/t/perspective-alarm-status-table-event-value-column-scaling-formatting/73845>\
**Category:** Ignition\
**Tags:** ignition81, perspective\
**Created:** [May 17, 2023, 3:31pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-status-table-event-value-column-scaling-formatting/73845 "2023-05-17T15:31:44Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![gino.miucci](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gino.miucci/32/19542_2.png) [@gino.miucci](https://forum.inductiveautomation.com/u/gino.miucci)\
**Post date:** [May 17, 2023, 3:31pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-status-table-event-value-column-scaling-formatting/73845/1 "2023-05-17T15:31:44Z")

</div>

I have a 'double' data type tag which has a format of 2 decimal places, which has an 'Above Setpoint' alarm enabled.

When the tag has a value of 22.68 and I set an alarm threshold of 20.5, the alarm appears in the Perspective Alarm Status table.

The tag itself shows a trigger value of 23.4 in its alarm EventValue property, however in the Perspective Alarm Status table object the 'Event Value' column for the alarm displays a value of 23.399999618530273

Is this correct behaviour for the Event Value column, or is there a way of formatting data in the Event Value column to show only 2 decimal places?

---

<div class="post-metadata">

**Author:** ![justinedwards.jle](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/justinedwards.jle/32/37854_2.png) [@justinedwards.jle](https://forum.inductiveautomation.com/u/justinedwards.jle)\
**Post date:** [June 4, 2023, 4:16am UTC](https://forum.inductiveautomation.com/t/perspective-alarm-status-table-event-value-column-scaling-formatting/73845/2 "2023-06-04T04:16:44Z")

</div>

I had an idea on this. I'm not sure how practical it is for your usage case, but I was able to achieve the desired effect by moving the alarm to a derived tag or an expression tag.

**Example:**  
Actual event value = 82.687545776

Tags:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/0/40f5711425ccf98593b45f3ac1f9f1e5d7b01747.png)  
TestTag01 has the raw value and TestTag02 has the expression value

Expression:

```auto
round({[.]TestTag01.value}, 2)

```

**Result:**  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/c/0/c078ab739a943f3ad199051578db63490c3e815e.png)  
Both alarms have the same trigger value, but TestTag02 displays with only two decimal places.

Here is how that looks in a derived tag:  
 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/3/63471fbc3370d8d8c5c3cacca9bb1e12215a3d32.png)

---

<div class="post-metadata">

**Author:** ![gino.miucci](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/gino.miucci/32/19542_2.png) [@gino.miucci](https://forum.inductiveautomation.com/u/gino.miucci)\
**Post date:** [June 12, 2023, 3:09pm UTC](https://forum.inductiveautomation.com/t/perspective-alarm-status-table-event-value-column-scaling-formatting/73845/3 "2023-06-12T15:09:20Z")

</div>

Very neat idea!

My tag was originally a reference tag (pointing to an MQTT Engine tag), so I changed it to a derived tag and applied the read expression exactly as shown, and now it works! 🍾

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/6/0/608b5a6582d671291cc790fc599a6d874ed98d45.png)

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/8/7/8779f309a8895bb0577faed9e0a2e30f6ce8c133.png)

I'm a little disappointed not to get any official response from IA as to whether the alarm object display should respect the source tag formatting for displaying data, but am happy I have a neat workaround.