Cascading value lists filter the values available for one property based on values previously selected for other properties. They are useful to help users select only correct combinations of related property values.
For example, refer to the following table of standard values for the properties Name, Project, Contract, and Contact. Without cascading value lists, a user could easily select unrelated values. Cascading value lists would only present valid values for Project that are related to the value selected for Name, values for Contract that are related to the value selected for Project, and values for Contact that are related to the value selected for Contract.
| Name | Project | Contract | Contact |
|---|---|---|---|
|
Addison Homes Ltd. |
AHL-1678-UC |
1678UA-A01 |
Bill Higgins |
|
Addison Homes Ltd. |
AHL-1678-UC |
1678UA-A01 |
Jock Wallace |
|
Addison Homes Ltd. |
AHL-2006-03 |
JR54 |
Jane Foresyth |
|
Blue Sky Construction |
CY345 |
CTN-56782 |
Hans Lustenhower |
|
Blue Sky Construction |
CY345 |
CTN-56782 |
Jim Wallace |
|
Blue Sky Construction |
CY345 |
CTN-76554A |
John Wilson |
|
Blue Sky Construction |
CY345 |
CTN-76554A |
Steve Maloney |
|
Blue Sky Construction |
CY346 |
CTN-4511-C2 |
Edwin Forsythe |
|
Blue Sky Construction |
CY346 |
CTN-4511-C2 |
Jim Robinson |
|
James Properties |
JP1165-A |
ZD43567 |
Dan Smith |
Configuring lookup lists is described in the following topic. The preceding example table would require four levels of cascading value lists. The same technique can be used for any number of interrelated properties.