Set multivalue parameter in designer

[Darren]

Hi,

Is there a way to set the value of a multivalue parameter in the data source wizard for debugging purposes?  The design time property value I mean.

Thanks,
Darren

[Squall]

Have you tried the approach explained in http://www.telerik.com/help/reporting/designing-reports-parameters-using-multivalue-parameter.html 

SN

[Darren]

I mean I would like to just type it into the designer as a design time property for testing purposes...

Like so:

'QX', 'AA', 'EF'

Something like that.

[Steve]

Hello Darren,

Currently the expression editor does not support list of values. But you can do that in the report constructor right after InitializeComponent like this:

this.ReportParameters["MyReportParameter"].Value = new string[] { "QX", "AA", "EF" };

Greetings,
Steve
the Telerik team

[Ioan]

how about two years later?

[Stef]

Hi Ioan,

Please check the updated help article regarding multivalue report parameters - Using Multivalue Parameters.

Regards,
Stef
Telerik

 

 

[Kyle]

So there's basically still no way to do this at design time? That article still doesn't suggest any way to do this. This is very frustrating from a development standpoint.

[Stef]

Hi Kyle,

Please check the Specifying Default Values for a MultiValue Parameter section of Using MultiValue parameters.

You can use the Array built-in function to specify multiple initially selected values. The listed values must be available in the ValueMember fields of the parameter.


Regards,
Stef
Telerik by Progress

[Kyle]

I still can't preview the report doing this though. If I try to set design-time parameters using "Array" it says something along the lines of "undefined function reference Array". So what you're suggesting works when the report is opened in the browser, which at that point I'll just pass those parameters myself since I'm using the HTML5 viewer.

Also, I ended up just using an object data source and passing the parameters in from the client side (JavaScript), as Object parameters. Then I convert them to the appropriate types (List<int>) and call the stored proc.

This was necessary anyways as the parameters have to be sent to the proc as a user-defined Table type.

[Stef]

Hi Kyle,

Multivalue parameters are evaluated as arrays of object, and require additional handling in the SQL query to be turned into a custom variable.

In addition to the found by you approach, you can use a stored procedure in which values are read, turned into a Table-valued parameter that is passed to another stored procedure.

Regards,
Stef
Telerik by Progress