After trying to figure it out in my head, it occurred to me to add message actions after each real trigger action to discern where this trigger error occurs.
The issue seems to be that when I load the value from a nonexistent array index into a variable (having just processed the final value in my loop feed array), I can’t execute the following expression:
if(len(@Variable.Loop Scan Value ) = 34, right(@Variable.Loop Scan Value , 12), @Variable.Loop Scan Value )
Not sure which part of this is failing, but will think through how I can use IFNULL() (new to me in LTS 14 vs. LTS 8) or LINK() to resolve…
Confirmed through button triggers that the @Variable.Loop Scan Value was indeed null (not emptystring).
I tried to use ISNULL() (not “IFNULL()”, which isn’t a function) in an IF() wrapping my original expression, but this still resulted in the trigger error:
if(isnull(@Variable.Loop Scan Value ), ‘NONSENSE FILTER’, if(len(@Variable.Loop Scan Value ) = 34, right(@Variable.Loop Scan Value , 12), @Variable.Loop Scan Value ))
However, splitting this into two adjacent trigger actions did resolve the error, but the first action ended up essentially being a longer-winded version of LINK() replacement of null values…
