|Bookshelf Home | Contents | Index | PDF|
Use Trigger and Target Feature tables when you want the values to appear in a UI control to change depending on a selection in another UI control. For example, if you want to display a set
|Bookshelf Home | Contents | Index | PDF|
Use Trigger and Target Feature tables when you want the values to appear in a UI control to change depending on a selection in another UI control. For example, if you want to display a set of values in either inches or centimeters, use a UI control tied to a Trigger table to allow a user to select Metric or Imperial. Based on that selection, a drop-down list tied to a Target table displays a set of values for Centimeters or a set of values for Inches. This relationship is shown in Figure 9.
Target tables allow you to create multiple sets of data (row types) for the same table. The Target table is a Feature table whose rows are defined by one or more row types. A row type is one particular set of values that appears if the user selects a certain value from the trigger table.
The Trigger table defines a relationship between its Code values and the named row types in the Target table. The field values in a Trigger table column are used to dynamically set the active row set for the Target table.
In the Trigger and Target example of a drop-down list that displays metric and imperial measurements, the UI control tied to the Trigger table gives the user the option of selecting Metric or Imperial. The UI control tied to the Target table displays one of two sets of values:
In the Target table, there are two row types: Metric and Imperial. You create these row types in the Target Feature table editor. By default, the Feature table designer creates a row type named table_DATA, where table is the name of the table. The CODE values for both sets are the same (for example, SM, MED, LG). The Description column contain the values for each set of data. Data in the Configuration table references only the single set of CODE values, so no extra work is required in the Configuration table to make reference to multiple row types in the Target table.
NOTE: A browser-based application offers unconstrained selections, that is, users can move freely from UI control to UI control, making selections from a complete list of options, and can go back and change selections without restriction. Trigger and Target Feature tables should be used only in cases where they best serve the us