Oct 11, 2022 05:09 PM
Any tips on how to set up a database to do QA (Quality Assurance)?
The main issue is that every project has different requirements and questions, so using one table seems like a no go.
The only constants in the whole database are three:
*(But, content of questions changes from project to project)
Everything else requires a unique ID
Should I create a different table for each new project?
Solved! Go to Solution.
Oct 13, 2022 04:12 PM
Oct 11, 2022 06:04 PM
Or should I create a “Questions” table, and somehow use it for all questions? And link/relate everything back to its Customer.
Even if each one is different?
Oct 11, 2022 06:48 PM
Welcome to the Airtable community!
A key piece of information for knowing how to structure your base is knowing how people will be entering data in the base. Will people be filling out native Airtable forms without access to the base? Will users be collaborators on the base interacting with a grid view? Will you have a 3rd party form system or a 3rd party portal system?
If you need to gather data using native Airtable forms, each unique question needs to be its own field. One record would have a set of questions and answers.
On the other hand, collaborators on a base could have a table of questions and answers, with one field for the question, and one field for the answer. Each record would represent a single question and answer.
Oct 11, 2022 07:29 PM
Yes, the idea is for people doing the Quality Assurance, the anonymous users, to fill a native Airtable form.
Initially thought about creating a native Airtable form for each Project, but I can see this approach will quickly get out of hand as the number of projects grows.
Want to avoid depending of 3rd party services like Zapier and would prefer to keep everything in one place (Airtable), or 2 places. Open to suggestions about any existing solutions that integrate well with Airtable either using its API or Webhooks.
Will check Jotform from this Airtable blog. Also Wordpress seems like another popular platform.
Thanks, as a new user I can see this will be useful, to handle entries per Record in the same table called “Questions”.
Even though each Project will be different, from my previous experience doing previous QAs, the number of rows hopefully will reach a certain point at which I will be able to reuse the same rows (example a “type of question”) for different Customers.
Oct 13, 2022 04:12 PM
I was approaching this the wrong way, as the solution is to use rows.