# Device State Table Report if Greater than 0 **URL:** \ **Category:** Help\ **Tags:** experience, dashboard\ **Created:** [July 22, 2019, 3:10pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018 "2019-07-22T15:10:12Z")\ **Posts on this page:** 9\ **Page:** 1
**Author:** ![Leo\_Bach1](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Leo\_Bach1](https://forums.losant.com/u/Leo_Bach1)\ **Post date:** [July 22, 2019, 3:10pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/1 "2019-07-22T15:10:12Z")
I have 4 attributes (alarms) that I am monitoring using a device state table in a dashboard which can be seen here: ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/0/04208a1c697077ebc3aac3b0fbd43fc5fc4c448c.png) The way these attributes work are that when there is an alarm they report the value of the alarm that occured… at all other push times they report zero. But I really only want to see the record (event) listed in the device state block if one or more of these attributes were greater than zero. I know there is probably a way to use the handlebar helpers to do this but could anyone provide an example of how I could do this? It would be extremely helpful to have experience user events but I know that this is not yet available and there is no set release date. Thanks! Leo ---
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [July 22, 2019, 3:24pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/2 "2019-07-22T15:24:01Z")
Hi @Leo_Bach1, You are correct, this can be done with Handlebars! I made an example with three devices (Alarm 1, Alarm 2, and Alarm 3) that report 0 when there is no alarm and a string error when there is an error. In my Device State Block, I use the #ne (not equal) conditional block helper to display _only_ when there is a string: ![20%20AM](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/0/02588de9beaf8deefcf65b61cea6208d87a07911.png) In your use case, you could use the #gt (greater than) helper to determine if something is greater than 0. Let me know if I can help further, Julia ---
**Author:** ![Leo\_Bach1](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Leo\_Bach1](https://forums.losant.com/u/Leo_Bach1)\ **Post date:** [July 22, 2019, 3:52pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/3 "2019-07-22T15:52:44Z")
This definitely helped clear out some of the extraneous information: ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/4/4369269e66744e36cdb6c63f91cb5737c290c449.png) Is there a way to remove the device name and timestamp unless one of the 4 other values are greater than zero? In any case it is better than it was before. ---
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [July 22, 2019, 4:29pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/4 "2019-07-22T16:29:35Z")
Hi @Leo_Bach1, The way the Device State Block is currently configured, there is no way to reference the attribute value within the Device Name cell. However, I will create a ticket for this with our engineers! Thanks, Julia ---
**Author:** ![Leo\_Bach1](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Leo\_Bach1](https://forums.losant.com/u/Leo_Bach1)\ **Post date:** [July 22, 2019, 4:34pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/5 "2019-07-22T16:34:18Z")
That would be helpful. Although, this is really being used as a workaround for an Event List or Open Event Idicator Block. If one of these dashboard block types could be filtered for Experience Users then I wouldn’t bother with the Device State block. ---
**Author:** ![Leo\_Bach1](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Leo\_Bach1](https://forums.losant.com/u/Leo_Bach1)\ **Post date:** [July 23, 2019, 8:23pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/6 "2019-07-23T20:23:05Z")
Looks like the losant engineers have been busy! Were these tags and filters just made available for Open Event Indicator and Event List blocks? ![image](https://us1.discourse-cdn.com/flex015/uploads/getstructure/original/2X/5/5f6b9aae668edc0d3e7254ca52f51eee0433ff74.png) Looking great so far! ---
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [July 23, 2019, 8:35pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/7 "2019-07-23T20:35:40Z")
Hi @Leo_Bach1, Very observant! 🥳 A Platform Update just went out, I will include a link to the detailed announcement when it is published on our blog. However, I believe the new changes to Events may be the answer in your use case. Four new Event Nodes have also been released, you can check out the documentation here: > **[Event: Create Node](https://docs.losant.com/workflows/data/event-create/)** > > Learn more about the Losant Event: Create Node. > **[Event: Delete Node](https://docs.losant.com/workflows/data/event-delete/)** > > Learn more about the Losant Event: Delete Node. > **[Event: Get Node](https://docs.losant.com/workflows/data/event-get/)** > > Learn more about the Losant Event: Get Node. > **[Event: Update Node](https://docs.losant.com/workflows/data/event-update/)** > > Learn more about the Losant Event: Update Node. Thanks! Julia ---
**Author:** ![Leo\_Bach1](https://avatars.discourse-cdn.com/v4/letter/l/ad7895/32.png) [@Leo\_Bach1](https://forums.losant.com/u/Leo_Bach1)\ **Post date:** [July 23, 2019, 8:47pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/8 "2019-07-23T20:47:30Z")
Spectacular work, Losant Team! This is certainly a step in the right direction that comes from this all too common question: I got an alarm… now what? It seems to me that keeping track of how an organization reacts to events and changes in their systems is a good place to start answering this question. ---
**Author:** ![JuliaKempf](https://sea1.discourse-cdn.com/flex015/user_avatar/forums.losant.com/juliakempf/32/2446_2.png) [@JuliaKempf](https://forums.losant.com/u/JuliaKempf)\ **Post date:** [July 24, 2019, 3:25pm UTC](https://forums.losant.com/t/device-state-table-report-if-greater-than-0/2018/9 "2019-07-24T15:25:03Z")
Hi @Leo_Bach1, The Platform Update article can be found [here](https://www.losant.com/blog/platform-update-events-modbus-serial-tensorflow-edge). Thanks! Julia