Forum Discussion
MarkShnier__You
Qrew Legend
5 years agoThe right way to do this is to have a table of Pricing Levels and then set up a relationship where one standard level is used on many projects.
And instead of having a multiple choice field your project table will pull in the level from the pricing levels table.
If you have a lot of existing data, you will want to set the key field of that table to be the level number. Actually in your case I would set the key field to represent the level number. Then when you make the relationship you can base it on your existing multiple-choice field and that existing multiple-choice field will get turned into a drop-down field where the choices come from the pricing levels table.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------
And instead of having a multiple choice field your project table will pull in the level from the pricing levels table.
If you have a lot of existing data, you will want to set the key field of that table to be the level number. Actually in your case I would set the key field to represent the level number. Then when you make the relationship you can base it on your existing multiple-choice field and that existing multiple-choice field will get turned into a drop-down field where the choices come from the pricing levels table.
------------------------------
Mark Shnier (YQC)
Quick Base Solution Provider
Your Quick Base Coach
http://QuickBaseCoach.com
mark.shnier@gmail.com
------------------------------