Set up a cascading parameter in the IUIE
On this page:
- Overview
- Cascading parameter restrictions
- Parameter that depends on a single parent parameter
- Parameter that depends on more than one parent parameter
Overview
Cascading parameters allow a value for one report parameter to determine the values allowed for another parameter. In this document, the terms "parent" and "child" refer to parameters that participate in a cascading relationship. A parent parameter can have many child parameters, and a child parameter can have multiple parent parameters in a cascading relationship.
Cascading parameter restrictions
Parent parameters must always appear above (that is, have a lower parameter sequence than) associated child parameter(s). Child parameters participating in a cascading relationship must have a widget type of
or ; other widget types are not supported. Parent parameters may be a , , or , provided they are not a child of another parent parameter.Parameter that depends on a single parent parameter
To set up a parameter that depends on a single parent parameter:
- On the Parameters page, scroll down to the parameter (child) to be cascaded, and then scroll right to change the widget type to either
If you set the widget type to
, set the Display Size value to the number of listbox entries that are visible without scrolling.
or .
- In the "Valid Values" column for the parameter, click the
WHERE
clause that includes a reference to the parent parameter (such as##PARM:<Parent Parameter Tech Name>##
).Example 1: Following is an example of a possible parameter-specific
WHERE
clause value of the child parameter when the parent parameter Valid Value codes are in the same table as the child Valid Value codes. In this example, the parent parameter isPARNT_PARM_CD
, and the parent code column isPARNT_CD
:PARNT_CD in (##PARM:PARNT_PARM_CD##)
Example 2: The following example uses a sub-select to reference a different table that relates parent to child. In this example, the parent parameter is
PARNT_PARM_CD
, the parent code column isPARNT_CD
, and the child code column isCHILD_CD
:CHILD_CD in ( SELECT CHILD_CD FROM MY_PARNT_CHILD_T WHERE PARNT_CD in (##PARM:PARNT_PARM_CD##))
icon. On the Edit Values page, enter an appropriate parameter-specific
Parameter that depends on more than one parent parameter
To set up a parameter that depends on a more than one parent parameter, repeat the above steps, and then enter a parameter-specific
WHERE
clause that includes a reference to both parent parameters, for example:
CHILD_CD in (
SELECT CHILD_CD
FROM MY_PARNTS_CHILDREN_T
WHERE PARNT1_CD in (##PARM:PARNT1_PARM_CD##)
AND PARNT2_CD in (##PARM:PARNT2_PARM_CD##))
In this example, the parent parameters are
PARNT1_PARM_CD
and PARNT2_PARM_CD
, the parent code columns are PARNT1_CD
and
PARNT2_CD
, and the child code column is
CHILD_CD
. This example uses a sub-select to reference a table that relates multiple parent codes to a child code.
You can enter clauses as either parameter-specific or synonym-specific, but note that synonym-specific
WHERE
clauses apply globally to all uses of the synonym by all reports. Different reports sometimes use different names for the same parameter, so it is best to enter cascading
WHERE
clauses as parameter-specific. For example, the GT report ADM_APPL_GT
uses the parameter
ACAD_CAREER_CD
, but the PDQ report
IE_SIS_ADM_APPL
names the same parameter
ACAD_CAREER
, and so the parameter-specific
WHERE
clause for the GT would refer to this parameter (for cascading parameter support) as
##PARM:ACAD_CAREER_CD##
, whereas the PDQ
WHERE
clause would use ##PARM:ACAD_CAREER##
.
Related documents
This is document azfo in the Knowledge Base.
Last modified on 2023-07-18 10:24:06.