Master and slave

The DBLookup being filtered is the slave input field. This field is called Job in the previous example. The input group that is used to filter the DBLookup is the master input field. This field is called Project in the previous example. First create the master and slave relationship, and then create the filter in the slave input field.

Note: The master-slave relationship will not work with hidden master DBLookups.

Multiple masters for one slave input field are also possible. Multiple masters are useful when you want to display only the jobs that are relevant for the selected project and department.

If you configure DBLookup filtering and the user does not select a master input field value, the user will not receive the same list in the slave DBLookup as they would if you had not configured DBLookup filtering. This issue occurs because the filter views a blank entry in the master input field as an "Any" value. Therefore, the filter displays every item in the slave input field that is associated with any of the items in the master DBLookup list. Some items in your database may not be associated with any of the items in the master DBLookup list, and they are excluded from the slave DBLookup list.

Using the same example, if there was a job called Training that was not associated with any of the projects in the Project DBLookup list, the Training item would not display on the Job DBLookup list when DBLookup filtering has been configured.