In Airtable/relational databases, you shouldn't need to create one column per product. Doing so is often considered bad practice. Instead, you can create a table of unique products and link this table to your Orders table using linked record fields. If you need to capture more metadata on the order -> product relationship such as different shipping dates per product per order or to create an itemized invoice, you can use a junction table approach.
This would look like this:
Orders (unique list) <-> Invoice (junction table) <-> Projects (unique list)
Structuring your data correctly will pay dividends later when it comes to producing the views/automations you need. Good luck!
In Airtable/relational databases, you shouldn't need to create one column per product. Doing so is often considered bad practice. Instead, you can create a table of unique products and link this table to your Orders table using linked record fields. If you need to capture more metadata on the order -> product relationship such as different shipping dates per product per order or to create an itemized invoice, you can use a junction table approach.
This would look like this:
Orders (unique list) <-> Invoice (junction table) <-> Projects (unique list)
Structuring your data correctly will pay dividends later when it comes to producing the views/automations you need. Good luck!
that is what I am trying to do, i got this initial structure from an excel file
that is what I am trying to do, i got this initial structure from an excel file
Ah got it. Sorry, I misunderstood your ask. Are you looking for a way to ingest future excel files that are in this format or do you only need to convert it once?
It looks like you need to pivot/transpose your Excel data before it comes into Airtable. Creating field values from column names in Airtable will require custom scripting.
