Hey all,
Jordan Barker sent his flow with predictive and API. I'll share next week. Plus plans for the next (2) meetings gradually take shape (keep you posted).
This week, we were working on flows with missing data, ie where we manually need to include missing data fields. To stop the flow running without us having added these missing data fields, we're testing "message" and the crew macro "blocking test". Anyone has an experience to share on those?
Best,
Thanks for your reply Hakimipous!
Yet we are looking for a way to stop/halt a flow when a certain condition is met. The blocking test should work, but when we use !Null() as expression, the test does not return errors. It seems the CReW macro "Blocking Test" does not recognize the NOT (!) operator (yet)?
Another possibility would be the Message tool (OPTION 1 "When To Send Message" = Before Rows Where Expression is True; OPTION 2 "Message Type" = Error - And Stop Passing Records Through This Tool) but this only takes the first column into consideration. The rest of the table/data frame seems to be ignored.
At this moment we haven't found an easy way to alert Alteryx users when data input contains NULL values. (Apart from the Field Summary tool, but this is slow on large data sets and requires the user to go check whether there are values missing. Additionally, it does not stop the flow from running.)
If anyone knows a smart method for blocking flows and/or alerting users when data sets contain NULL values (or other conditions), please let us know!
Thanks,
Vadim
I've found this
I guess it's related to your issue ?
Hey all
With some delay because of other priorities ...
Not sure if this helps, but I tend to use the standard tools "block until done" and "test" instead of the CReW macros, which I expect comes down to the same.
For example, in a flow doing some complex allocation logic etc, I make sure that in = out ; if not OK, then the Test tool will fail the flow before I start writing to the target table.