cascading drop downs "many to one" relationships


Posted by Jdubs - Feb 3 ’15 at 09:52

What's the best way create cascading drop-down menus via Plumsail Lookup that have "Many to One" relationships?


For instance, what if 2 (or more) cascaded drop-down fields depend on the SAME primary drop-down value?


Currently, we're duplicating the primary drop-down value.  This causes issues down-stream because even though the primary value has the same name, it has a different ID value.


Pic 1:!3814&authkey=!ABORHzQbUTa4F4k&v=3&ithint=photo%2cpng


Pic 2:!3815&authkey=!APbGCceeI-x4HUY&v=3&ithint=photo%2cpng

  • Dmitry Kozlov
    Dmitry Kozlov
    Member for: 8 years 7 months 26 days
    #1 by Dmitry Kozlov Feb 4 ’15 at 05:00

    Unfortunately, I haven't got the structure of your lists. Could you provide the schema with relationships and a screenshot of a form containing cascading drop-downs. If you have more than one parent, you can design cascading drop-downs based on 3 combo boxes: grandparent - parent - child.

Displaying 1 to 1 of 1 messages