Is my Airtable setup correct?

I am developing software for car appraisers in Softr and have structured my database with five tables:

  1. Enduser (Appraiser) - Unique identifier: Email of the appraiser
  2. Clients of the Enduser - Unique identifier: Email of the client (One appraiser can have multiple clients)
  3. Vehicles of the Client - Unique identifier: Vehicle registration number of the client (One client can own multiple vehicles)
  4. Appraisals of the Vehicle - Unique identifier: Report number of the appraisal of the client (Each vehicle can have multiple appraisals)
  5. Payments for the Appraisals - Unique identifier: Payment number of the report number (Each appraisal can involve multiple payments)

Is this structure appropriate? One potential drawback is that when importing data into related tables, I can only link one table at a time. Ideally, when I add an appraisal along with the vehicle’s registration number, the system should automatically identify the associated client (based on the vehicle registration numer) and the corresponding enduser (since the client is linked to the enduser).

Hi Floris,

I think your table is fine, it is proper management to split the parents and children structures in different tables. In terms of your question regarding the linking, you can do this with automations. I will add though that having 5 layers of linking can become quite complex to link it all together properly, so take your time with it. I am open to help you do this if you can’t figure it out but I will have to charge my fee and I would highly recommend trying it yourself first :slight_smile:

1 Like