zero value considered as "is empty" constraint in data value changed trigger
Hi, I'm trying to get this campaign to trigger in the case of a new lead created OR if a data value change to Company Size is made, but only for previous values not included in the 0 to 500 range.
The issue is that this campaign in now also triggering on data value chage when previous values was 0. Seems like the "is empty" criteria is where these leads are triggered - Marketo would mix up null and zero?
How can we make it makes the difference between Null and zeros? Is there anything related to how the variable is configured in SF?
Re: zero value considered as "is empty" constraint in data value changed trigger
Hey Alex,
You'll probably want to use this "Is Not" operator in this case where you would say: Data Value Changes, Previous Value is Not "0, 0-500" Specifying 0 will distinguish the value from null.
Re: zero value considered as "is empty" constraint in data value changed trigger
Hi - I work with Alex. We tried to do that , but the constraint does not allow ranges (0-500) nor multiple numbers 0,1,2,3 for this field. I still don't get why "is empty" constraint would let 0 values in.
.png)