Hi @Customer_Service, and welcome to the community!
This suggests that you need a different data model architecture. You need to virtualize the intersection of styles, pricing, length, width, zipper sizes, etc. Have you thought about collapsing 16 window styles into a single select field?
As @Bill.French said, it doesn’t sound like you’ve optimized the setup of your system properly.
Instead of using fields to manage all of those items, you will probably want to use multiple different tables & records instead.
If you have a budget for this project and you’d like to hire an expert Airtable consultant to help you create this, please feel free to contact me through my website at ScottWorld.com.
Hi @Customer_Service, and welcome to the community!
This suggests that you need a different data model architecture. You need to virtualize the intersection of styles, pricing, length, width, zipper sizes, etc. Have you thought about collapsing 16 window styles into a single select field?
Thanks you! I did, I have pricing in a separate pricing tab, question is linked to the windows selection. I will not let me pick the same style twice.
Example: On one side of the boat there is 4 (B1, B2, B3, B4) windows - so I linked to window style selection (thinking we could train to enter windows in order) but if B1 and B3 are the same style it will not let me pick the same style twice.
