# How filter alarm by Associated Data in Perspective Alarm status table

**URL:** <https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762>\
**Category:** Ignition Early Access\
**Created:** [April 19, 2021, 5:07pm UTC](https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762 "2021-04-19T17:07:10Z")\
**Posts on this page:** 6\
**Page:** 1

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [April 19, 2021, 5:07pm UTC](https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762/1 "2021-04-19T17:07:10Z")

</div>

Hi  
Like the Vision alarm status table, I’d like to filter my displaying alarm by using Associated Data. This is really wanted feature if you want to upgrade the old vision project to perspective.

[https://docs.inductiveautomation.com/display/DOC81/Vision+Alarm+Status+-+Filter+on+Associated+Data](https://docs.inductiveautomation.com/display/DOC81/Vision+Alarm+Status+-+Filter+on+Associated+Data)

Now in the perspective alarm status table, we have a filter property that doesn’t have an option for Associated Data.

Is there any workaround for this right now?  
If not is there any plan to add this feature?

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [April 19, 2021, 5:14pm UTC](https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762/2 "2021-04-19T17:14:04Z")

</div>

> [@nader.chinichian](#):
>
> Now in the perspective alarm status table, we have a filter property that doesn’t have an option for Associated Data.

Are you sure? The `filterAlarm` function gets a standard alarm event; it should have access to the associated data just like Vision does.

---

<div class="post-metadata">

**Author:** ![nader.chinichian](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/nader.chinichian/32/9261_2.png) [@nader.chinichian](https://forum.inductiveautomation.com/u/nader.chinichian)\
**Post date:** [April 19, 2021, 5:22pm UTC](https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762/3 "2021-04-19T17:22:30Z")

</div>

> [@paul-griffith](#):
>
> `filterAlarm`

Oh sorry I didn't see that before, I always check configure events section for specific component event.

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [September 18, 2021, 8:24pm UTC](https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762/4 "2021-09-18T20:24:01Z")

</div>

with the perspective alarm status component, with filter property Diagnostic set to False,  
I still receive in the filterAlarm function the alarms with the Diagnostic priotity.

It seems that the priority “filter” condition is applied after the **filterAlarm function.**

I think that perhaps for better performance, it will be better to apply the filterAlarm function (which read associated data) after all component filters (priority, source, etc)

In my use case, I have better performance adding a test on priority inside filterAlarm before checking associated data.

---

<div class="post-metadata">

**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\
**Post date:** [September 20, 2021, 4:14pm UTC](https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762/5 "2021-09-20T16:14:49Z")

</div>

Hmm, the code for both the status table and journal queries for the alarms first, then applies the filtering from the extension function. There might just be a different issue with the priority filtering in general; can you get in contact with support?

---

<div class="post-metadata">

**Author:** ![mazeyrat](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/mazeyrat/32/10955_2.png) [@mazeyrat](https://forum.inductiveautomation.com/u/mazeyrat)\
**Post date:** [September 21, 2021, 6:43am UTC](https://forum.inductiveautomation.com/t/how-filter-alarm-by-associated-data-in-perspective-alarm-status-table/45762/6 "2021-09-21T06:43:28Z")

</div>

Thanks, I will check again and post a ticket if necessary.