I’ve been trying to add associated data to some alarm notifications, but every time I receive a consolidated message the associated data gets returned as “null”.
For context this is the format of the consolidated message in the notification block (with some additional formatting tweaks):
<html>
{alarmEvents.Count} alarm events have occurred:
</html>
<html>
{{
Alarm "{label}" at "{ScopeL2}" transitioned to {eventState} at {eventTime|hh:mm:ss}<br>
}}
</html>
The {ScopeL2}is associated data we use to filter alarms in Ignition.
In a normal message of a singular alarm the associated data does get resolved normally, but in a consolidated message it seems this data is not available.
Is there a way to use this associated data in a consolidated message? Or could that be possible in the future?
Have you tried to see if it is an HTML issue? Try sending a plain text version just as a test.
Also, because it is consolidated, perhaps the second/final alarm doesn’t have the associated data and the Null you see is a result of the that alarm overwriting the first or previous alarms that started the pipeline.
The message used to be plain text and still had the same issue, the html has been me experimenting with formatting to clean it up so to speak (the <br> for new lines per alarm wasn’t something we had previously).
On the overwriting note, I would find that strange, we require all alarms to have this feature for filtering and they all have this data inherited from the UDT. My hypothesis is that this associated data is not saved for the consolidated message hence the returning of null, though I have no actual proof that this is the case.
