Community
Participate
Working Groups
Cascading parameters currently only allow selection of one item per list. It would be very useful to be able to allow multiple selections per list. The simplest case is when multiple selection is only allowed for the final parameter in the cascading group. In this case we allow the user to select multiple options on this last list and use these in our report (e.g. in an "in" clause of a sql query). A more complex case is when multiple selection is allowed on other parameters in the group. In this case, when a user selects multiple values for a parameter, the values for the next parameter list in the cascading group would need to include the values relevant to all selections, presumably removing duplicates. The groundwork has been laid for this in the engine by bug id 206464. The other things needed to do would be to allow cascading parameters to be flagged as allowing multiple values in the designer, handling these in the viewer, and ensuring multiple values are dealt with properly for these when submitted to the engine.
(In reply to comment #0) > Cascading parameters currently only allow selection of one item per list. It > would be very useful to be able to allow multiple selections per list. > The simplest case is when multiple selection is only allowed for the final > parameter in the cascading group. In this case we allow the user to select > multiple options on this last list and use these in our report (e.g. in an "in" > clause of a sql query). > A more complex case is when multiple selection is allowed on other parameters > in the group. In this case, when a user selects multiple values for a > parameter, the values for the next parameter list in the cascading group would > need to include the values relevant to all selections, presumably removing > duplicates. > The groundwork has been laid for this in the engine by bug id 206464. The > other things needed to do would be to allow cascading parameters to be flagged > as allowing multiple values in the designer, handling these in the viewer, and > ensuring multiple values are dealt with properly for these when submitted to > the engine. Any news about the activity for the request for enhancement? One thing we've come across in BIRT is that it seems that multiple selection of parameter values is not allowed with cascading parameters. There seems to be some desire for that in the community, with one request for enhancement entered into Bugzilla, 208477, Allow cascading parameters to allow multiple selections, https://bugs.eclipse.org/bugs/show_bug.cgi?id=208477. It seems to be scheduled for BIRT 2.3.0. Will support for multiple selection of cascading parameters be included in BIRT 2.3? While waiting for 2.3, is there a workaround for this problem? We also tried using multiple selection of parameters (not cascading) but didn't succeed. Clicking on the data set we saw the error text in italic below. The report parameter {0} allows multiple values, which can not be used to link with data set parameter. However, we read http://www.birt-exchange.com/modules/wfdownloads/singlefile.php?cid=2&lid=233. The key thing in taking care of the multiple parameters here seems to be having a filter in the output dataset. However, this is not an optimal solution since the filtering is done after the query. Down below is a little bit on how this can be solved in SQL Server reporting. Would it be possible to do this filtering before calling the data set and subsequent filling with data? We're using Eclipse BIRT all-in-one 2.3M5 and java 1.6u3. Initial work for us has gotten BIRT to work with stored procedures together with input parameters. Works fine. Now we want to go further and convert some of our old reports to BIRT. In those old reports we use multiple selections in cascading parameters. In the reports, we convert multiple parameter selections to a comma-separated string before calling associated stored procedures. We've done exten Below how the work goes: ---------- For a call to stored procedures: - a number of input parameters - input parameter usually a string (which consists of comma-separated values) CREATE PROCEDURE [owner].[stored_procedure_name] @param1 as VARCHAR(max), @param2 AS VARCHAR(max), ..., @param_n as VARCHAR(max) = NULL DECLARE @sql NVARCHAR(max); SET @sql = 'SELECT ... '; EXEC sp_executesql @sql,... when @sql gets its value, the comma-separated input values get splitted into proper values for the sql statement. e.g. SET @sql = '....' + ' AND table.column IN (' + split param1 into proper values + ')' + ... ---------- In SQL Server reporting, before calling the stored procedures, the input values to the stored procedures (comma-separated strings) are constructed using the Join command which splits the values into comma-separated values. Would it be possible to provide ability for multiple selections in cascading parameters in BIRT together with something similar to the Join command? Then the rest might be up to the users responsibility? Lars Johansson
*** Bug 231345 has been marked as a duplicate of this bug. ***
Would it be possible to add a new option to the set-up of a simple parameter's dynamic dataset "re-evaluate this parameter's dataset when any other parameter changes" (default 'no' for compatibility). This would solve the problem both for cascaded parameters and simple parameters based on datasets with interdependencies. There would have to be a check for cyclic dependency, preferably at the time of definition.
Need more investigations.
Move to future for more investigation.
*** Bug 218588 has been marked as a duplicate of this bug. ***
As shown in http://www.scribd.com/doc/15350321/BIRT-Multi-Value-Cascading-Parameters is is possible to select multiple values from a cascading parameter listbox. However, that seems work only when using the automatically generated parameter page. Would it be hard to add support for using a custom parameter page (via JSP tag library) ?
We support multiple values for last child in cascading parameter group now. Need investigation whether to support the complex case.
*** Bug 298488 has been marked as a duplicate of this bug. ***
Hello, anyone news about the complex multiple? so values also for parents lists?
Hello, any news on this issue. The solution described on http://www.scribd.com/doc/15350321/BIRT-Multi-Value-Cascading-Parameters with Birt 4.6 doesn't work anymore. Thanks
