Variable filter after merge variable node

[takbb]

Yes, definitely +1 from me for a Variable Filter node.

In discovering the issue raised by the following question, I realised that the ability to filter out Flow Variables would have been the perfect solution!

Merge Variables Node - Only first input updates during a loop

We are trying to build a component within a recursive loop which takes widget inputs, and passes the new variables back to the start of the loop. This is run on Server (but the question is independent of Server): 2 issues came up: Recursive loop end does not pass back variables to the start of the loop (even if the variables are in the data stream). The solution to this seems to be to convert the variables to another table and use 2-port Loop Start and End. The second issue is the Merge Varia…

So it isn’t just a need to remove superflous variables, but a single flow split into different processing streams and then merged back via Merge Variables will always result in the flow variables from the first input stream trumping the flow variables from inputs 2 and 3, as there is no way to filter them out.

From the Merge Variables documentation:

“Note: If there are the same variables defined in different inputs, the standard conflict handling is applied: Top most inputs take priority and define the value of a variable.”