Hello everyone,
Has anyone encountered an issue with Slack notifications where a correlation rule successfully retrieves the device IP address for one fault parameter, but fails to retrieve it for another fault on the same element?
In our Slack integration run script, we have a field reserved for Extended Info. We use the following syntax to retrieve the device IP address:
*TEXT-Bold "IP":*[parameter(field(dmaid),field(eid),2003,field(idx))]</span>
This pulls the IP address from the Element, device IDX table using Parameter ID 2003.
What I’m seeing is intermittent behavior where testing a fault on one parameter correctly displays the IP address in the Slack alert, but testing a fault on a different parameter does not display the IP at all.
Has anyone seen similar behavior related to correlation rules, IDX context, or parameter scope differences between alarms?
Please see the below examples


Thank you @dino that solved the issue and I can now confirm IP address displays in the slack notification for every fault condition.
I get the impression that this question has already been answered in the comments. If this is indeed the case, could you select this answer to indicate that the question can be closed and no further follow-up is needed?
Yes, this question has been resolved.
TY
Hey Juan! I believe the issue is the 2003 parameter is not using the same index as the alarm that is not showing the IP.
The syntax of [parameter(field(dmaid),field(eid),2003,field(idx))] means show the value of the 2003 parameter, using the DMA ID, Element ID, and IDX of the intital alarm.
In the case of the Temperature Fault, the IDX is "1", which I believe matches up with the IDX of the table you're grabbing the IP from (2000). In contrast, the Input Video Source fault appears to be using "Proc #2" as the IDX which in this case does not match the IDX of the 2000 table.
If the IP you're wanting to display is always going to use the IDX of "1" I suggest hardcoding the IDX into the syntax, making it appear as follows:
[parameter(field(dmaid),field(eid),2003,1)]