Parameter with multi select not shown

[Gregory Kohle]

Hi,if I try to add a parameter with multi select then dropdown is not shown. If I try this without the multi select enabled then the dropdown is shown. Single select: Multi select: If there is no multi select then everything is working. But if there is multi select then the report is stuck at loading and no drop down list is shown. Here is my configuration for the parameter: The option of default values is set to none. Is there an option to set to get it working?Thanks. Regards,Patrick

[Vinoth Srinivasan]

Hi Patrick, 

Thanks for your interest in Syncfusion components. 

We were able to reproduce the reported issue at our end. A support incident has been created under your account and we request you to login into our Direct Trac support system for further updates on this issue. Our Direct Trac support system can be accessed from the following link: 

https://www.syncfusion.com/account/login?ReturnUrl=%2fsupport%2fdirecttrac%2fincidents 

 

Regards, 

Vinoth S. 

[Gregory Kohle]

Hi Vinoth,

thanks for your reply.
I also noticed, that when I want to add a parameter with a datetime datatype or integer datatype, an error occurs.

Shift is an integer parameter. Here is the configuration:

Is there something that I configured in the wrong way?

Here is the datetime configuration:

This is the error message:

Is there something that I have to configure in another way?

Thanks.

Regards,
Patrick

[Vinoth Srinivasan]

Hi Patrick, 

 

We suspect that the error occurs due to the dataset field datatype mismatch with the query parameter. So, we request you to ensure both the dataset field and query parameters having same data type. If you still face any issue then we request you to share the report with dummy data to reproduce the issue at our end. It will be helpful for us to provide the solution at the earliest. 

 

Regards, 

Vinoth S. 

[Gregory Kohle]

Hi Vinoth,

I checked the values and they are of the same type.
I attached the report with a test database.
You just have to add "and Layernum in (@Shift)" at the end of the query for DataSet1 to get the error.
For the datetime value you can change EvalDate > '02.01.2017' to EvalDate > (@Startdate) and the error should be there.
Thanks.

Regards,
Patrick

Attachment: Error_Report_505a5cd1.zip

[Gregory Kohle]

Hi Vinoth,

could you reproduce the error using the report and the test database?
Thanks.

Regards,
Patrick

[Vinoth Srinivasan]

Hi Patrick, 

 

We have tested the shared report with your database and we were not facing any issue while processing the query parameter in our report designer. We have prepared a video sample based on this and it can be downloaded from the following location. 

 

http://www.syncfusion.com/downloads/support/forum/129773/ze/QueryParameter1118699644 

 

Also, for the parameter “Shift” the value field of “Available Value” is “Layernum” and the value field of “Default Value” is “ShiftName” so it throws an exception while running the report in both Microsoft report builder and in our report designer. So, we modified the data field “Layernum” in available and default value of the parameter and the modified report can be downloaded from the following location. 

 

http://www.syncfusion.com/downloads/support/forum/129773/ze/Einzelmaschine1969184569 

 

Regards, 

Vinoth S. 

[Gregory Kohle]

Hi Vinoth,

thank your for the response.
What I noticed in the video is that you use a hardcoded value for the date and shift parameter.
When I use this in the report then it is working on my side as well.
This problem occurs only when I use [@Shift] or [@Startdate] as the parameter value.
Thank you for pointing out the problem with the default and available values for "layernum".

I hope this will help you reproduce the issue.
Thanks.

Regards,
Patrick

[Vinoth Srinivasan]

Hi Patrick, 

 

We must provide any static parameter values to the pop up showed in query designer to retrieve column details for the data set. When run the report, it will automatically retrieves the data from dataset based on the parameters. We have tested the query parameter value as in your snap with MS report builder it shows the same error in data type conversion, please refer the below screenshot. 

 

 

So, we request you to use the static default values while run in query designer. 

 

Regards, 

Vinoth S. 

[Gregory Kohle]

Hi Vinoth,

thanks for your answer.
I got it working now.
You just have to convert it like this:
convert(varchar, DBParameter) in (@ReportParam)

Regards,
Patrick

[Vinoth Srinivasan]

Hi Patrick, 

Thanks for your update. Please let us know if you require any further assistance on this. 

Regards, 

Vinoth S.