nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

avoid multi-step process when using report parameters

csetzkorn

I am a birt newbie. When I run a web report I seem to have to first chose the values of the report parameters before I can view the report. After that, I can change the report parameters whilst viewing the report. Can I avoid the first step and run the report with some, ideally database driven default report parameter values? Hope this makes sense.

Find more posts tagged with

Comments

mwilliams

So, you want the first run to not take a value or take any value from the database, then, allow the user to choose their own values if they want to change them?

Matthew L.

The only way I would know how to accomplish this is to use a redirect report that will hyperlink to another report design.
You could set default parameter values on the Actual report, then create a Launcher report that has a label (with a bookmark assigned to it) in it that has a hyperlink to the Actual report. Then use client side scripting to locate the label via its bookmark and use an auto redirect to the link.
 
Attached is my example that was created for the Actuate iHub3 environment.