Forum Discussion
I'm wondering if there was a solution to this? I think of it as an issue of not being able to 'uniquify' data natively in Quickbase. 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
------------------------------
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
------------------------------
- MarkShnier__You6 years ago
Qrew Legend
The problem is that the child table may contain duplicate missing parents. So a saved table to table import will fail as the import contains duplicates for the Key Parent field..
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------- OanaWhalen6 years agoQrew CadetI actually was envisioning skipping the table to table import altogether. With my checkbox method, you can trigger an automation every time a record is added to Table A, with the action being create one new record in Table B IF the parent record does not exist. Since this is a one-by-one automation, even if it trips over itself and tries to add the same record to Table B twice, all you get is an error message with no impact on the automation running for other records being added. Since the record is added to Table B already, the error doesn't matter.
------------------------------
Oana Toma
------------------------------- MarkShnier__You6 years ago
Qrew Legend
Yes, I do use that method, so we are in the same wavelength.
The issue can be if data comes into the app in grid edit or mass import or a sync table, and there is not the opportunity to trigger record by record.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------