I’ve setup a beautiful multi-table Airtable database system for one of my clients, and we’ve got 5 different tables that are all linked to each other & working perfectly. :slightly_smiling_face:
But now — we’re interested in creating a form where our volunteers can be in the field and submit brand new data into the database. In other words, this submitted data is brand new data that will need to be spread out across the multiple tables & linked across multiple tables.
I know that none of this is currently possible with Airtable’s built-in form capabilities, because Airtable forms don’t currently support:
Creating new linked records from a form.
Adding new data into a linked table’s fields via a form.
So, I know that this can’t be done with Airtable’s native form tools.
But I’m wondering if anybody has their “personal favorite solution” for automating this process? I’m thinking of a few different solutions, but I was wondering what you guys have found to be the best solution on your end! :slightly_smiling_face:
Some of my ideas are:
Build a form in Airtable that just dumps all the new information into a brand new table that is created just for collecting form submissions, and then have people manually copy & paste the data into the appropriate tables.
Same as above, and then trigger an automation in Integromat or Zapier to put the data into the appropriate tables.
Build a form in another platform (such as JotForm or FormStack or TypeForm), and then use Integromat or Zapier integration to put the data into the appropriate tables.
I suppose that #1 through #3 are all pretty much the same concept (using Airtable’s built-in form builder to dump raw data into a different table), and #4 involves switching to another platform for the form building capabilities.
Any bright ideas on this topic? Am I missing something here?
Hi @ScottWorld - based on our discussions yesterday, you know I’m going to go for option 2, right? :slightly_smiling_face:
Option 1 is fine, but manual
Options 3 & 4 aren’t what I would go for in this situation as it sounds like the full solution can be contained in Airtable. I’m a big user and fan of Zapier, but usually when I want to connect Airtable to X or Y. If I want to connect Airtable to itself, then, with the introduction of the script block, this feels like a better solution.
Hee hee, absolutely! :slightly_smiling_face: And I think you make a very strong argument for this. If it can be done within Airtable, best to keep it within Airtable.