Dynamic lists trouble...

[ollyrouse]

Good afternoon all,

 

Really hoping someone can point me as to where I am going wrong on the attached file?

 

[Layout: CookingRecord]

I can make my portal display the data required, but the user interface is not what I need.

Upon clicking in the first field ("Product ID") a drop-down list displays showing all the related data from the table ("PRODUCT").

What in fact I want to do is filter these lists in a much better way.

 

What I need is:

• a user to click in the field ("Product Type") in the portal (this displays a drop-down list of all the records in the related table)
• when a selection is made the next field in the portal ("Product Specific") displays a drop-down list, but only the records in common with the first value
• when the selection is made in both the drop-downs, the ("Product ID") could be filled in - displaying all the other related data

 

Please let me know if I've not explained myself clearly.

 

Many thanks indeed for your time

Olly

 

 

cooking.fmp12.zip

[The Big Bear]

Olly

I do not have FM12 but in FM10 when you make your value list click on the box that states " Include only related values starting from" and chose the filed you want to display.

 

Hope this helps

Lionel

[eos]

See if this is the conditional value list you want. Of course you should see that the Product entries don't have all the same specs (and don't put a popup on it …), or this menu doesn't make any sense (as would the specifics field itself).

 

btw, I'm thinking that maybe you should use some sort of ProductSpecifics table connected to Products table, seeing that at the moment you have/need two entries for Beef in your Products table just to accommodate different specifics. Look into “database normalization”. 

 

from Olli to Olly 

cooking_aBiteos.fmp12.zip

[ollyrouse]

Hi all,

 

Thanks for the tips... however I think I'm somewhat mis-understood...

 

Hopefully this diagram better explains the functionality?

 

TIA - you're help is always appreciated

 

Olly

 

 

 

cookingApp.pdf

[eos]

I guess your illustrations made clear what you want, but that isn't necessarily the best solution for the problem at hand.

 

Try this one; you must think about what goes where, but basically this is a normalized structure. Now selecting a product will give you a selection of existing variants for that product and fill in the fields. To create new variants, simply go to the respective product, create a new record in the portal and fill in the specs. The next time you select that product for a CookingRecord, the variant will appear in the popup.

 

I assume you replicated the fields in the join table to be able to adjust them for the respective event/dish; otherwise you could just display the related fields from Products or ProductVariants, respectively.

cooking_eos_trulyRelational.fmp12.zip

[ollyrouse]

eos,

 

Thank you so much! This is exactly what I needed to achieve. Seriously helped me out and made me smile - full steam ahead!

 

Hope you have a great day and thanks again

 

Regards

Olly

[ollyrouse]

Alas... I'm back 

 

eos - please can you work your magic on this again? 

 

Attached is my file, and a new screenshot of what I need to do - The TO's totally confuse me still?

It's likely I will need to do this same function again on another table also... I'm hoping I'll be able to work it out by then!

 

Many thanks indeed if you get the time...

 

Olly

[eos]

Alas... I'm back 

Attached is my file, and a new screenshot of what I need to do

 

Neither of those are attached.

[ollyrouse]

2nd Attempt?

Archive.zip

[eos]

eos - please can you work your magic on this again? 

 

There is no magic; in fact, you could learn it …

 

In the first place, make sure you're using a value list that indeed puts in an ID in your ID field, instead of a name. Secondly, add a TO of the table where the values for your new value list live, and create a relationship between this TO and the TO of the layout where you want to use the CVL. Then create the CVL by using the first TO as the field source, and the second TO for the "Starting from…" option. (You now have two examples to study this mechanism.)

 

Then I really! recommend using pop-ups instead of drop-downs, unless you're interested in seeing raw IDs. If you use a value list with two fields (presumably an internal ID and a human-friendly name) and the option to only show the second field, then a pop-up can resolve the ID you actually put in (field 1) into the corresponding name (field 2), so you get the best of both worlds. A drop-down cannot do that; since it allows input of arbitrary values, it must allow field entry and thus reveals the actual field contents, i.e. the ID.

cooking_eos_trulyRelational_v00000002.fmp12.zip