Custom SQL Alert Trigger Condition not translating Variable ReferencesW

c.gura

We are doing a Alert Trigger condition using Custom SQL Alert. Here is the following code:

I want to alert on: Custom SQL Alert (Advanced)

Set up your SQL condition: Node

SELECT Nodes.NodeID, Nodes.Caption FROM Nodes
, (SELECT * FROM ntta_monitor_alert_procedures
WHERE alert_procedure = 'no-email'
AND AlertName = '${N=Alerting;M=AlertName}') AS sc
WHERE Nodes.NodeID = sc.nodeid AND Nodes.NodeID = ${N=SwisEntity;M=NodeID}

This seems to be a bug that the variable is not recognized

The variables are not working. We are using the Web based alerts.

I have even tried adding single ticks around the variable name, but that just makes the variable look like a string so the SQL validates fine, but it does not translate the variable to the value expected.

xtraspecialj

I think I'm experiencing a similar issue.  As far as I know the Condition is working fine, however, in the alert message SQL variables (macros with custom SQL statements inside of them, like: ${SQL: SELECT Caption FROM Nodes WHERE NodeID = ${N=SwisEntity;M=NodeID}}) are not getting resolved.  I've tested our SQL code extensively and it is resolving the ${N=SwisEntity;M=NodeID} variable inside of the SQL statement, but it's just spitting out the entire code in the alert message...

Did you ever get your issue resolved and, if so, what was the deal?

SOLVED: Well, not really solved I suppose.  More like, figured out.  When the Trigger Condition is a custom SWQL condition, SQL macro variables in the alert action message don't work for some reason (at least when the type of object to be alerted on is "Volume Forecast Capacity".  Maybe this problem isn't prevelant with other object types, but I suspect that it is.).  I imagine this will get fixed if/when they allow custom SWQL macro variables in alert action messages instead of just SQL.  It's kind of curious how when creating the web alert engine they added the new Custom SWQL Trigger Condition option, but didn't also add custom SWQL alert action variables as well.  Anywho, once I changed the condition to SQL, converted my SWQL code to SQL (which was kind of a pain since "Volume Forecast Capacity" isn't a choice of Object to alert on when using SQL, but it is when using SWQL...), and redid my test action message, all was well.