Expressions in Inbound Filters

Wade Shelton
Thu, 11 Mar 2021 17:42:57 +0000
Integrator.io

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:

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

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 posts - 2 participants