Automations turn off after an error
I'm trying to add a value from Table A as a unique primary key into Table B. However, sometimes there are duplicate values in Table A, so I WANT them to error out and not be added to my table. However...
Forum Discussion
MarkShnier__You
Qrew Legend
Qrew LegendI do have a native solution for this but I'm tied up on client projects right now. Contact me directly if you would like one on one assistance and are in a hurry or else when I have a chance I will post back to this thread.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
MarkShnier__YouQrew Legend
Qrew LegendWell I'm so far behind what I need to get done today, I guess another 5 minutes won't hurt. So to the Community this is your isolation gift of the day as a reward for sitting indoors "Staying at Home".
Automation (overnight) or a URL formula button runs a saved table to table import to import all records into the same table merging on [Record ID#] to update each record missing a parent with the current date and time into a field called [Date/Time Parent Create Requested].
Automation called Request Creation of Parent Numbers triggers on [Date/Time Parent Create Requested] and subject to the filter that the child is missing a Parent then Action = updates a field called [Actually Create Parent date / time] with the current date/time.
Automation called Actually Create Parent triggers on [Actually Create Parent date / time] and subject to the filter that the child is missing a Parent, creates the Parent.
I have not fully wrapped my head around why this does not exceed the rate threshold limits for Automations given that the process is initiated b y a saved table to table import which in my test was a mass update of 32,000 children records needing 1,000 parents created and it worked with only 1 error on duplicate Parent Key field.
It does not lot run especially fast, like at a rate in my example of creating a few parents a second like maybe 2 or 4 per second. But for small data sets needing parents or an overnight process, that slow rate will not be noticeable.
There is something about that two step Automation process with the filter on the Record ID# = Record ID of the Trigger Record which causes the Automations to queue up nicely and prevent the duplicates.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
Automation (overnight) or a URL formula button runs a saved table to table import to import all records into the same table merging on [Record ID#] to update each record missing a parent with the current date and time into a field called [Date/Time Parent Create Requested].
Automation called Request Creation of Parent Numbers triggers on [Date/Time Parent Create Requested] and subject to the filter that the child is missing a Parent then Action = updates a field called [Actually Create Parent date / time] with the current date/time.
Automation called Actually Create Parent triggers on [Actually Create Parent date / time] and subject to the filter that the child is missing a Parent, creates the Parent.
I have not fully wrapped my head around why this does not exceed the rate threshold limits for Automations given that the process is initiated b y a saved table to table import which in my test was a mass update of 32,000 children records needing 1,000 parents created and it worked with only 1 error on duplicate Parent Key field.
It does not lot run especially fast, like at a rate in my example of creating a few parents a second like maybe 2 or 4 per second. But for small data sets needing parents or an overnight process, that slow rate will not be noticeable.
There is something about that two step Automation process with the filter on the Record ID# = Record ID of the Trigger Record which causes the Automations to queue up nicely and prevent the duplicates.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------