Home Discussions Questions & Answers Understanding parameter validation rules

Understanding parameter validation rules

Avatar photoCustomer September 30, 2023 at 3:41 pm

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?

Viewing 6 reply threads
  • Author
    Replies
    • Support October 2, 2023 at 12:22 am  

      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.

    • Avatar photoCustomer October 2, 2023 at 10:19 am  

      And if I can use wildcards, does that mean ‘Validate From List’ is unchecked?

    • Support October 2, 2023 at 9:35 pm  

      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.

    • Avatar photoCustomer October 5, 2023 at 12:33 am  

      If I need to modify the LOV query for just one parameter without affecting others that use the same LOV, how should I proceed?

    • Support October 5, 2023 at 3:58 am  

      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.

    • Avatar photoCustomer October 7, 2023 at 12:59 am  

      Can I save an ad hoc LOV I create using ‘LOV Custom’ so others can reuse it?

    • Support October 8, 2023 at 1:51 pm  

      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.

Viewing 6 reply threads
  • You must be logged in to reply to this post.

Login with: