In a Condition action, a field reference correctly shows as a formula (pill format) when the operator is ‘is less than.’ Switching the operator to ‘is equal to,’ ‘contains,’ or ‘matches regex’ causes the same field to revert to plain text and stop resolving, even after retyping. Is this a known issue, or am I missing a step?
Hi,
I wasn’t able to replicate this issue on my end. When I change my condition action rules between ‘is less than’ or ‘is equal to’ the values I have entered in either rules path (incoming data) or field path (comparing value in the conditional) don’t change from plain text to formula values or vice versa, so if that is really happening on your end, seems like it’s a bug.
I will say that having an incoming payload as a number 1 and entering 5 in my condition action field (whether as a formula or as plain text) shows up in the event viewer as this:
"field" :1,
"value": "5"
which technically shows the conditional value as always being a text value, but the condition action was able to correctly compare the results in both scenarios.
Are you able to share the exact data payload and condition you are trying to compare, or maybe at least a sanitized mockup version so I could see if your specific data and/or calculations may be causing an unintended outcome?