the question part of this discussion? is it rhetorical?
Put that to music and you've got a hit.
Ok, i thought that was funy Actually just poor writing.
But besides the more or less fun part. What do I need to do to get a third level into these drop downs?
I actually would not name it Flavour but lets say "Dish" which (hopefully) means kind of meal (?).
So should I generate a new table called Dish and Link that to Item of the the Table Order?
If I understand your question correctly, let's expand the example from the documentation with your request for a third value, "Dish".
TYPE ITEM DISH Record 1 Lunch Soup Chicken Noodle Record 2 Lunch Sandwich Corned Beef Record 3 Lunch Hamburger Cheeseburger Record 4 Dinner Chicken Chicken Kiev Record 5 Dinner Steak 8oz Record 6 Dinner Fish Halibut Record 7 Dessert Cake Chocolate Record 8 Dessert Pie Apple Record 9 Dessert Pudding Chocolate Record 10 Lunch Soup Tomato Record 11 Lunch Sandwich Peanut Butter Record 12 Lunch Hamburger Banquet Burger Record 13 Dinner Chicken Chicken Parmesan Record 14 Dinner Steak 12oz Record 15 Dinner Fish Salmon Record 16 Dessert Cake Vanilla Record 17 Dessert Pie Pumpkin Record 18 Dessert Pudding Tapioca
To build a value list that would show appropriate values from Dish, you would build a relationship to the table, like so:
startingTable ∞ Menu_byTypeAndItem
TypeSelectorField = Type
ItemSelectorField = Item
where TypeSelectorField and ItemSelectorField are global text fields.
And the value list, let's call it Dishes, would show Related Values in the Dish field from Menu_byTypeAndItem, beginning from the startingTable table.
If you were to set TypeSelectorField to "Dinner" and ItemSelectorField to "Steak", the value list would contain the values "8oz" and "12oz".
I hope I understood your question correctly and, if so, I hope this helps answer it.
EDIT: I just scanned the example from the help file more thoroughly; it looks as if it's describing a self-join situation, in which case you would simply match Type and Item to themselves in a self-join relationship (as opposed to using the global text fields). I hope that makes sense.
1 of 1 people found this helpful
There are actually quite a few ways to set up conditional value lists, as well as design alternatives that recreate the function of a conditional value list but with features that cannot be built into an actual value list and thus use other layout objects and scripts to achieve the desired result.
You may find these two example files useful sources of both conditional value lists and "enhanced" value selection methods. The first file includes several different working examples of hierarchical conditional value lists--value lists where selecting a value in list one filters what values appear in list two--that then filters what values appear in a third list...
This is so stupid! Its was actually not the logic behind it that keept me hours working on it, I had blanks in every "type" field that I doubled to generate variants for the dish :/
Attached is the basic file. Maybe its not the best way to do it but it works. I really wonder why filemaker is not posting demo files.
And sorry or the German dishes
Now I am hungy!!!
Rouladen und Spätzle, bitte.
Looks good to me, and it works... now you just have to add onObjectModify script triggers to your Type field to clear Item and Dish, and to your Item field to clear Dish, so that you don't end up with combinations like Dessert / Sandwich / Ribeye.