Home › Discussions › Questions & Answers › Understanding parameter validation rules
Customer · · Questions & Answers · 7 replies
I am working with a report parameter where I must select a value from the list, but for another parameter, I can freely type in something like ‘AP%’ to filter. What controls this difference in behavior?
This behavior is determined by the ‘Validate From List’ setting on the shared List of Values (LOV). If this setting is checked, the parameter validation enforces the selection of one record from the LOV and does not allow the use of wildcards.
And if I can use wildcards, does that mean ‘Validate From List’ is unchecked?
Exactly. If ‘Validate From List’ is unchecked, the parameter value is not validated against the LOV, and the use of wildcards, such as ‘%’ or ‘_’, is allowed. This behavior is part of how the Parameter Type definition controls validation at run-time.
If I need to modify the LOV query for just one parameter without affecting others that use the same LOV, how should I proceed?
If you want to modify the LOV query only for the current parameter, switch the parameter type to LOV Custom before making modifications. Note that changing a shared LOV affects all parameters referencing it.
Can I save an ad hoc LOV I create using ‘LOV Custom’ so others can reuse it?
Yes, if you create an ad hoc LOV using ‘LOV Custom’, you can click the ‘Save as shared LOV’ button to make it available for other report parameters.
Sign in with LinkedIn or Google to take part.
