If you became a customer of the Syncfusion� Reporting Platform or the Report Viewer, Report Designer, or Report Writer components before October 2019 and have questions related to those products, you can request support through our forum system. However, please note that this support system is only for existing customers who are still using the Syncfusion� Reporting Platform or its components and not for new customers looking for reporting products from Syncfusion�.

For new customers or those with general reporting questions, we recommend contacting our support team at https://support.boldreports.com/, which is a separate brand created by Syncfusion� for its reporting solutions. Our team will be happy to assist you with any questions you may have.

Thank you for choosing Syncfusion� for your reporting needs.

Cannot use null value for parameter if other parameter cascades from first one

Hello SyncFusion Experts,

I have a report with cascading structure of parameters:

Parent parameter - combobox that is optional - list is taken from the WebAPI.
Child parameter - multi select that is optional - list is taken from the WebAPI but Parent parameter is the parameter of API action (part of filter).

After I configure Parent parameter to allow null value, the report viewer is forcing me to choose one. I thinkt this is because Child parameters require it.
If I try to set "Allow null value" for child parameter then I've got a message: "Multiple default values were specified. The parameter does not allow multiple values." Default value is set to none and Available Value is set to Query Value for child parameter.

Is there any way to set those parameters as nullable (not required) so report user will not be forced to select values for them?


1 Reply 1 reply marked as answer

MS Muthuramana Sankaranarayanan Syncfusion Team March 2, 2021 01:58 PM UTC

Hi Kamil, 

We checked your query. We are following the SSRS reporting standard. As per SSRS reporting standard null value for multi value parameters is not allowed. Hence we also do not have support for this. We suggest you to have a null value with your WebAPI datasource and handle this at your end by selecting the null value at the time of report preview. 

Please let us know if you have any queries regarding this. 

Regards, 
Muthu Ramana S 


Marked as answer
Loader.
Up arrow icon