...
Excerpt | ||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
Lookups consist of a Lookup Group and Lookup values, which contain at a minimum a Code and Decode value. For new lookups, first create the lookup group. To add or configure a lookup:
You are returned to the Lookup Groups list. To add values to the new group:
|
...
Excerpt | ||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
The application allows lookup field filtering based on another dataform field, allowing you to configure filtered field functionality on data forms. The filter values are defined using the Filter Value field, on the Lookup Detail. So, using Status/Category as an example, given the following configuration, if you pick Category1, then the status field will be filtered to show only Status1, Status2, and Status3:
This filtering also allows for comma separated values (do not leave spaces between your values) in the Filter Value to provide an OR mechanism so that, in this case, the Status can live in multiple categories. So, given the following configuration, Status1 would show up when both Category1 and Category2 are selected:
Dataform Configuration The dataform configuration for lookup fields has been enhanced points to point to another field on the form as a Source for its filter. There is now a Filter Source field, under the Filter Value field, when configuring a lookup field on a dataform. You put the ID of the field that you want to be the Source for our filter. When that field's value changes, our field will be filtered with that value. So, using the example configuration above, if we had an luCategory and luStatus field on our dataform: in the field properties for luStatus we would enter the value luCategory in the Filter Source field. luStatus will now be is filtered as luCategory is changed. NOTE: This is NEXT only functionality. The Filter Source value is ignored in classic. If there is a value in both the Filter Value and Filter Source fields, NEXT will use Filter Source instead of Filter Value, but Classic will continue to use the Filter Value field.the system uses Filter Source.
|
...