Home › Discussions › Questions & Answers › Using Logical Expressions for Multiple Values Parameter Check

Using Logical Expressions for Multiple Values Parameter Check

Avatar photoCustomer Questions & Answers 9 replies

I want to enable the ‘Multiple Values’ checkbox for a parameter so users can input a list of account numbers. What specific criteria must the parameter’s SQL text meet for this checkbox to be available and function correctly?

9 replies

  • Support Enginatics

    The SQL text must include a bind variable restriction using one of the following comparison operators: =, , !=, like, or not like. Crucially, for the multiple values functionality to work by substituting the `IN-clause`, the table column must be on the left side of the comparison operator.

  • If I implement a parameter using this multiple values feature, how does Blitz Report handle the substitution of the bind variable at runtime?

  • Support Enginatics

    When the ‘Multiple Values’ option is enabled, the single bind variable syntax used in your SQL (e.g., `:p_account_number`) is intelligently substituted with a comma-separated list of values enclosed within an IN-clause during the report execution phase.

  • We need to implement a complex GL Account Analysis report using multiple input parameters. Can Blitz Report handle these complex parameters while still providing formatted Excel output?

  • Support Enginatics

    Yes, complex parameter implementation is standard. You can define various parameters for filters like GL Balance, specific time periods (YTD), or hierarchical nodes. Blitz Report ensures the final output, regardless of complexity, is delivered as a perfectly formatted Excel file.

  • If we were migrating a Discoverer report that relied heavily on cascading parameters, how easy is it to replicate that functionality?

  • Support Enginatics

    Blitz Report is an effective Discoverer replacement. Parameter functionality can be configured using internal LOV lookups or custom SQL LOV types, allowing developers to replicate complex cascading parameter dependencies efficiently within the Blitz Report interface.

  • We need to track every time this report definition is modified, including changes to the parameter constraints.

  • Support Enginatics

    The system mandates strict control. Every modification, including parameter changes, is logged and maintained as full version control with audit comments tracked inside your EBS instance, ensuring complete report definition traceability.

  • You must be logged in to reply to this post.