Hi Dojo,
I wanted to create an alarm template with some conditions. But I guess the problem is the different index in the tables, because it's not working.
Table:
The overall SRT Inputs Status CC Error Rate is the base, if there is an error already I don't want to see the other tables here complaining about CC Errors as well.
I used this condition for SRT Input Components and SRT Input Status Services:
Does it not work like I want because the index is different?
4.a7651a0c-e841-4579-954b-5f7be84470f0
4.a7651a0c-e841-4579-954b-5f7be84470f0.4.1
4.a7651a0c-e841-4579-954b-5f7be84470f0.0 etc.
Hi Alberto,
this should work for every row in the table. This one is just an example.
Hi Stefan,
You are right, it doesn't work because there is no direct relation between the two tables.
There are 3 relevant tables, all linked via foreignKey=14000 (SRT Inputs Table):
- SRT Inputs Table (14000) — Master config table, one row per SRT input
- SRT Inputs Status (11200) — TS-level stats, 1:1 with SRT Inputs (one status row per input)
- SRT Input Components (3000) — PID/service-level detail, 1:N with SRT Inputs (multiple rows per input)
Both 11200 and 3000 use 14000 as the join point, making them siblings rather than parent/child. Alarm template conditions can only reference columns within the same table (same row) or columns from a direct parent table (via foreignKey), so cross-referencing between sibling tables is not supported.
Have you tried if you add "*" or "?" in the filter?
E.g. *Mediaset Italia* or Slot 4*
I believe in your case could work also with the display key – but if not, I'd try by filtering on 4.a7651*