Automations turn off after an error

Question

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, the automation automatically shuts itself off after one error. This is really annoying because I still want the automation to continue even if there is an error.

For example:
Table A
1:10
1:11
1:10

Table B
1:10
1:11

That is the final structure I'd like.

I understand that it doesn't want to run into infinite loops, but that isn't what's happening here.

Is there any way to do this with automations, or do I have to write a custom script to populate this table with a loop checking for duplicates?

quickbasejunkie · Answer

Have you considered a table to table import? You can set it up to merge records with the same ID.You can then automate the import with an Automation.

lucasbuxman · Answer

Hi all,I'm wondering if there was a solution to this?&nbsp; I think of it as an issue of not being able to 'uniquify' data natively in Quickbase.&nbsp; I see a suggestion to 'use a t2t import' to do this but that will fail if Table A has multiple records that are desired to be uniquified as a primary key in Table B.There has to be a better way than pulling that data out of QB and pushing it back in after uniquifying in a separate tool.------------------------------Lucas Buxman------------------------------

markshnier__you · Answer

I 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
------------------------------

markshnier__you · Answer

Well I'm so far behind what I need to get done today, I guess another 5 minutes won't hurt.&nbsp; So to the Community this is your isolation gift of the day as a reward for sitting indoors "Staying at Home".Automation (overnight)&nbsp; 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&nbsp;Request Creation of Parent Numbers&nbsp;triggers on [Date/Time Parent Create Requested] and subject to the filter that the child is missing a Parent&nbsp; then Action = updates a field called [Actually Create Parent date / time] with the current date/time.

Automation called Actually Create Parent&nbsp;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.&nbsp;&nbsp;It does not lot run especially fast, like at a rate&nbsp; in my example of creating a few parents a second like maybe 2 or 4 per second.&nbsp; 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 ProviderYour Quick Base Coachhttp://QuickBaseCoach.commark.shnier@gmail.com------------------------------

oanawhalen · Answer

I'm not sure if this is exactly what you're going for, but I've used a pretty simple solution for something similar in the past. If you create a relationship between Table A (child) and Table B (parent) using your match field as the reference, you can create a Formula - Checkbox field in Table B called Parent Exists? or something along those lines. The formula in that checkbox is simply "true."

Now create a lookup field in your relationship, where Table A wants to pull down that Parent Exists? field. If there is a match in Table B already, that lookup with be populated with a checkbox. If there is not yet a match in Table B, and therefore the record in Table A is an orphan, the lookup will be blank.

You can filter your automation to only run when the lookup checkbox is Table A is NOT checked, and it will not try to create a duplicate record in Table B.

If your intent is to get an error message instead in Table A, you can probably use form rules or some more complicated code to get that to happen right when you enter the data and it realizes that box is checked. Alternately, if you want to force the Table A value to be unique, you can create a Formula - Text field that checks if the Parent Exists? box is checked, and if so, adds some unique identifier.

------------------------------
Oana Toma
------------------------------

Forum Discussion

Automations turn off after an error

Related Content

Delete Formula Button Error

404 Error on new nav

Automating Manager Approval via Email

Move attachment to SharePoint error

Pipelines automation to change record owner