Skip to content

A custom attribute meant to resolve to an email address (for use in a notification) doesn't seem to produce a value when referenced.

Answer

Isolate the custom attribute from the notification mechanism before debugging further — build a Quick Report using the same underlying expression but with a hardcoded key value in place of the dynamic reference; if the Quick Report returns the expected email address, the attribute definition is fine and the problem is in how it's being referenced from the notification, not the attribute itself.

← Browse Platform, Aurena, and customization questions