Filtering DBLookups

The application can be configured to use filters on DBLookups. Filtering DBLookups is useful to present only a relevant subset of selections to the user, based on a prior selection. For example, you can filter the values in the Job DBLookup on the Weekly Timesheet based on what is selected in the Project DBLookup.

There is no validation or security when you filter DBLookups. In this example, if you select a project and then select a corresponding job from the Job DBLookup, the system will not prevent you from then changing the project.

Note: The primary DBLookup supports multi-select and will display the relevant values in the secondary DBLookup.

Using this example, you can filter the Job DBLookup based on the Project DBLookup in four steps:

  1. Select Project 1 from the Project DBLookup.
  2. All job IDs that are associated with Project 1 are selected from an intermediate table linking the primary and secondary input fields.
  3. The PROJ_NAME_JOB table is joined with the JOB table using the JOB_ID field, thereby filtering the list of selectable jobs in the Job DBLookup.
  4. The job data for jobs for the selected project is displayed in the Job DBLookup.