I’d like to see an On/Off option (defaulted to Off as it is now) available for Schedule-type Events, when ForEachRowInTable is turned on, that makes the execution of the associated Process happen serially for each record, rather than in parallel like how it works now.
So I’ve created a ForEachRow Schedule Event that runs every night, it checks each [Location] against the existing Location records, and adds a new record if one doesn’t exist.
Here’s the problem though:
If more than one new record exists in the first Table, with the same new unique [Location] value, then the Bot is going to create more than one new Location record, with that same value. That is because the Event conditions are checked against every record at the same time, instead of one after another. (i.e. in parallel, instead of serially).
So I set up a ForEachRow Schedule event, that runs every morning, to add the records for each user per day.
The issue:
The Bot was originally set up with 2 Processes, one to add the Day record, and one to add the standard child records associated with each Day. I wanted to use something like MAXROW( Day , _RowNumber)
to auto-populate the Ref value in each child. The problem was though, that since the execution wasn’t done serially, every child record got associated with only one Day record, instead of spread out between the different record how they needed to be. i.e., there were 15 child records associated with one Day, instead of 3 child records each, across 5 different Days.
Thanks for reading and considering. Please let me know if the above makes sense, and if anyone else has other scenarios that could benefit from this feature.