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; } } }

Dynamically create Report Parameters in RPTDESIGN

Abhishek Birjepatil

Hi,
 
We are currently using a driver report for bursting and saving the output on a shared network location.
The driver report would be scheduled with the parameters.
A single driver report is able to execute different reports.
However, set of parameters can be different across different reports. The input parameters for the child report should be present in the DriverReport for it to Execute the child report.
 
<ol><li>Is it possible to dynamically create parameters using Script in RPTDESIGN ?</li>
<li>Can the value of a parameter be used in a function which fetches a list for a second parameter.</li>
</ol>Thank you,
Abhishek.

Find more posts tagged with

Comments

Matthew L.

To answer your questions:
1: Yes you can create parameters within a report design.
Per this example, it will create a new ScalarParameterHandle, set it to required, and set a default value (use in beforeFactory).
Then add it back to the same report its being run from:
<pre class="_prettyXprint _lang-js">
scalarParameterHandle = reportContext.getDesignHandle().getElementFactory().newScalarParameter( "Example Parameter" );
scalarParameterHandle.setIsRequired( true );
scalarParameterHandle.setDefaultValue( "Test" );
reportContext.getDesignHandle().getParameters().add( scalarParameterHandle ); </pre>
*Note, that unless you save the updated report, you will not see these report parameters, and you will have to run the report a second time in order to see these new parameters within the parameter page (See attached example for a demonstration on this behavior).
 
2: I'm not sure what you are asking for per this question, can you explain your use case in more detail?
*are you trying to create something like a cascading parameter effect between two completely different parameters?
 
Also have you looked into Actuate IDAPI, it could be helpful.
 
I've also attached an example that "could?" be useful.
The "Driver" report reads in the "Child" report's report design, extracts and copies all the parameters from the "Child" report into the "Driver" report.
So to demonstrate, you would run the "Driver" report once and you wont see any parameters asked.
If you run the "Driver" report a second time, you will now see the parameters that existed in the "Child" report appear in the "Driver" report (because the "Driver" report design has been updated).
Using this as an example, you could create a "Driver" report that auto updates itself per the specified "Child" reports, then you would just have to link the parameters between the "Driver" and "Child" reports when using it as a report launcher.
 
*Based on what I think you are trying to accomplish, this is how I would accomplish it:
Have the "Driver" report dynamically create a "Parameter" report based on the "Child" report's, the "Driver" report would have no user input, but instead generate the "Parameter" report and launch it automatically, which would give the user a parameter page to enter all the parameter values in, then once the user finishes entering parameter values, the "Parameter" report would launch all the "Child" reports by passing their respective parameter values.