Home › Discussions › Questions & Answers › Implementing Multi-Value Selection for Report Parameters

Implementing Multi-Value Selection for Report Parameters

Avatar photoCustomer Questions & Answers 5 replies

I need to configure a custom report parameter that allows users to select multiple values, similar to the multi-select functionality seen in standard concurrent requests. What configuration steps are necessary for Blitz Report parameters to support multiple selection?

5 replies

  • Support Enginatics

    Blitz Report parameters are highly flexible. You can define a custom list of values (LOV) by setting the LOV type to ‘custom’ when creating the parameter. The underlying SQL of your report must be written to handle the list of values passed by the parameter, typically using an Oracle `IN` clause.

  • Avatar photoCustomer

    Does Blitz Report provide tools to simplify the creation of parameters themselves, or must I define the full LOV validation logic every time?

  • Support Enginatics

    Key users can significantly simplify parameter creation by leveraging existing definitions. You can choose from any existing parameters already used by standard Oracle Concurrent Programs or the seeded Enginatics Blitz Reports. This saves effort on defining standard LOV validation logic.

  • Avatar photoCustomer

    If I copy an existing report to define a metric, how do I ensure the parameters are also carried over correctly?

  • Support Enginatics

    When creating a new report based on an existing one, like copying a seeded report (e.g., Order Header and Lines to create a DIFOT report), the parameters are retained or can be redefined in the new copy, maintaining change control wherever applicable.

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