A Report Rule condition checking whether a variable (like [#Email]) equals NULL always evaluates to false, even when the field is confirmed blank when the report runs — why doesn't a plain 'equals NULL' condition work, and how should this actually be checked?

All FAQ questions / Reporting and analytics

Answer

Report Rule condition expressions need actual values on both sides, so a literal blank/NULL comparison doesn't evaluate the way you'd expect. Wrap the check in a small SQL validation using NVL instead: set Expression 1 to [&SELECT nvl('[#Email]', 'true') FROM dual], the Operator to =, and Expression 2 to true — this correctly evaluates to true only when the variable is actually null/blank, sidestepping the direct NULL-comparison limitation entirely.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions