v8.1.28
I have a tag alarm with two associated data fields, one named EquipmentID and one named Equipment ID, both set to the value of 1234.
I updated the messages on the notification profile to include this data:
Message body:
EquipmentID: {EquipmentID} Equipment ID: {Equipment ID}
Consolidated message body:
{{EquipmentID: {EquipmentID} Equipment ID: {Equipment ID}}}
Next, I changed the tag value to trigger the alarm. I got the following in an email:
EquipmentID: 1234 Equipment ID: 1234
So far, so good.
When I add a second alarm to the same tag and set EquipmentID and Equipment ID to 12345, changing the tag value triggers multiple alarms and invokes the consolidated message, which resulted in the following email content with NULL values:
EquipmentID: 1234 Equipment ID: null
EquipmentID: 12345 Equipment ID: null
I'm assuming there is something extra required - apparently only in a consolidated notification message - to handle spaces in an associated data field name.
I have tried {'Equipment ID'} and {"Equipment ID"} and even {Equipment%20ID} with no luck.
This is obviously an abstraction of the real application, where I have multiple associated data fields defined and some have spaces in the names. I don't want to eliminate the spaces because it's (so far) the only way to set the column header text on an alarm table. As a workaround, I could modify hundreds of tags and create extra associated data fields without spaces that are bound to the ones with spaces...but of course would like to avoid that.
Any ideas on how to get this working properly?