Skip to content

For a SQL-type Quick Report, is there a way to make a parameter mandatory (by default they're all optional), and is there a way to set a default value for a parameter — and where is this documented?

Answer

Both are controlled through Query Flags, specified in square brackets between the ampersand and the parameter name, like &[mcsbl]PARAMETER_NAME — M makes the parameter Mandatory, C restricts it to Custom/simplified values-only entry, S restricts it to a Single value (its opposite allows multiple, semicolon-separated), B allows Between-range expressions, and L allows wildcards ('%' and '_'); any flag's opposite is specified with a leading '-', and the default flag set for SQL Quick Reports is [-CS-L]. For example, SELECT * FROM fnd_user WHERE identity LIKE '&[-CS-L]Fnd_User' uses the default flags explicitly. For default/enumerated parameter values, reference the source view and column together in the substitution instead of just the parameter name — &VIEW_NAME.COLUMN_NAME — which also pulls in the translated prompt label for that column; for example, '&CUSTOMER_INFO.CUSTOMER_CATEGORY_DB' shows the enumerated Customer Category values with its translated prompt, and this VIEW.COLUMN syntax can be combined with Query Flags together, like '&[-CS--]CUSTOMER_INFO.CUSTOMER_CATEGORY_DB'. This level of detail is covered in the Foundation1 Development Guide, under Business Report and Analysis Specific Development > Adhoc Reporting > Development of Quick Reports.

← Browse Reporting and analytics questions