Hi @noe1995 ,
Another construct might look something like this:
Exactly how the flows are joined depends on whether the output from both the DB Readers is compatible, and you might need to do something different with them depending on what comes after the CASE Switch End
The NoOp node is an extension from Nodepit Power Nodes. It’s purpose here is to do nothing other than provide a means for connecting an Empty Table Switch data port to the DB Table Selector’s flow port, thus controlling the flow.
If you don’t/can’t use the NoOp node, you can use the Add Empty Rows node instead. Other nodes would also work, but this one is pretty infallible and won’t waste processor! (I just configure it to add 0 additional rows, so that it is doing nothing.)
