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.
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.
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?