Expressions in Inbound Filters

Integrator.io
, , , ,
1

I have a flow where I'm performing a lookup against a custom table. I need use the results of that lookup in filters for downstream process to determine whether those steps should be run.

The JSON after the lookup looks like this:

5301043caa20740200000001-da9168343f3546bd98a4fb467886c865.png
5301043caa20740200000001-da9168343f3546bd98a4fb467886c865.png674×313 27.7 KB

In the step after the lookup, I have an expression-based filter set up:

5301043caa20740200000001-e95e54f4153d4ce9b64d26f4016e5138.png
5301043caa20740200000001-e95e54f4153d4ce9b64d26f4016e5138.png921×220 3.21 KB

Note that "PreviousDocumentData" is an Object array returned on successful lookups. If it exists, I don't want subsequent steps to fire.

I've tried using record.PreviousDocumentData in the expression and "is not empty" vs "is empty". In all cases the filter does not behave as I would expect. It either always allows the record to pass, or never does.

In the legacy UI, I would have just added the missing variable "data.PreviousDocumentData" and checked "is not empty", but I can't seem to make this work in the new UI. Any suggestions?

2

@wadeshelton
Thanks for posting this to the community! We have created a support ticket to look into this issue: #82274. In the meantime, a recommendation I received from our team is for you to use a JavaScript filter rather than a Rules filter.