We’re talking about
{% if %}
statements in HubL, right? Is this limitation documented somewhere?
I wonder if this is just one manifestation of a more general limitation.
I’ve been fighting for the last day and a half to get expressions working in
{% for %}
and
{% set %}
statements. These expressions use properties of the built-in
contact
variable, like what you’re describing in this Slack thread:
Courtney Fantinato
Is there any information on when contact properties/variables will be supported in if statements for email? Was trying to store a contact property value in a variable to then use in an if statement to set the value of a new variable (i.e. if airport code = YVR, set airport name to Vancouver), and realized it wasn’t working because if statements aren’t supported in email with contact variables.
Jon McLaren
Hi Courtney, totally understand the frustration and see the use case here. Its a known issue, and it is being looked into, Unfortunately there is no timeframe to disclose at this time.
It’s not working for me. HubL just doesn’t seem to be able to evaluate the expression when it occurs inside the statement. I have described the issue in a community post here, and on the Slack channel here and here.
Could the issue with
{% if %}
statements possibly be a more general issue with contact properties inside statements?