Configuring a secondary field in the SSP Timesheet

Administrators can configure DBLookup fields with primary and secondary relationships. Selecting a value in a primary field, for example Department, dynamically filters the available values in one or more secondary fields such as Project, Docket, or Dimension. To configure a secondary field that depends on a primary field:

  1. In the field's DbLookupUIParams, add the primary field's context key to the sourceParams property. For example, to filter a Project lookup by the selected Department, sourceParams='STRING==#control.DEPT_NAME#'.
  2. Use typed bindings to match the parameter's data type:
    • Use STRING== for text values.
    • Use INTLIST== for integer lists.
    • UseDATE== for date values.
  3. Add each referenced key to the field's DbLookupUIParams.sourceParams whitelist.

    The following example configures a Project lookup that filters based on the selected Department:

    multiChoice=falsesourceType=SQLsourceKeyField=PROJ_IDsourceParams='STRING==#control.DEPT_NAME#'source='SELECT PROJ_ID, PROJ_NAME FROM VL_PROJECT WHERE DEPT_NAME = ? ORDER BY PROJ_NAME'

    When the user selects Finance in the Department field, the Project lookup automatically shows only projects associated with the Finance department.