I don’t think that that sounds like the best way to structure your database.
Instead of duplicating your inventory across 3 different tables, the ideal way to setup your system is to keep all of your inventory in just ONE table, but create 3 different views that you can work out of.
So instead of 3 different tables, you would have 3 different views.
Then, whenever you make a change to a status, you only need to update it once.
My free Airtable training course discusses views in great depth.
I don’t think that that sounds like the best way to structure your database.
Instead of duplicating your inventory across 3 different tables, the ideal way to setup your system is to keep all of your inventory in just ONE table, but create 3 different views that you can work out of.
So instead of 3 different tables, you would have 3 different views.
Then, whenever you make a change to a status, you only need to update it once.
My free Airtable training course discusses views in great depth.
hmm yeah, I did forget to add that there are some differences between the tables that I wouldn’t want to be shown on the others (financing prices, etc) and I am not sure I am able to do that within the same table!
hmm yeah, I did forget to add that there are some differences between the tables that I wouldn’t want to be shown on the others (financing prices, etc) and I am not sure I am able to do that within the same table!
Yes, absolutely! Each view can be customized to only show the fields that you want to see!