Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.

0

Issue with Paginated Report Optional Parameters (Allow Null Value) Rendered As Required

Hi,

 

I have a paginated report with multiple parameters that allow null values. When I publish the report and try to run it, all the parameters are shown as required and I'm getting error "This field is required."

 

I tried re-publishing the report multiple times but that's not fixing the problem. I can run the report correctly directly from the Power BI Report Builder by leaving all the parameters blank.

 

My application is about to go live and I need to fix this asap, please help!

 

Thank you,

 

Erick

 

Erick

Status: Delivered
Comments
v-chuncz-msft
Community Support

@ERDIAZ 

 

This issue seeems to be fixed already. You may try the latest version of Report Builder.

ERDIAZ
Regular Visitor

@v-chuncz-msft,

 

Thank you for your reply. Unfortunately, that didn't resolve the issue.

 

I had Report Builder version 15.6.1613.2 so I downloaded the latest 15.7.1704.1:

 

PowerBIReportBuilderVersionjpg.jpg

 

I saved the report again with the new version of Power BI Report Builder, ran the report and make sure it still allows null:

 

PowerBIReportBuilderParametersAllowNull.jpg

 

Then, I published the report and the same issue still persist:

 

PowerBIReportParametersRequired.jpg

 

Any ideas?

 

Thank you,

 

Erick

v-chuncz-msft
Community Support

@ERDIAZ 

 

I tried the latest version to test several cases and all seem to be working fine. Try to recreate the file.

ERDIAZ
Regular Visitor

@v-chuncz-msft,

 

I'm not sure what do you mean by recreate the file? But if you are referring to redesigning the whole report, I'd rather avoid this as it’s a very complex layout and time consuming and would only consider it as a last resort.

 

I did try uploading another report under the same name just to make sure it wasn't a cache issue and, once I verified that the new report was rendering then I tried to publish again the original report but the issue is still there.

 

Thank you,

 

Erick

ERDIAZ
Regular Visitor

@v-chuncz-msft,

 

BTW - this is only happening with the parameters with dropdown lists. If you look at my print screen above, the parameters on the last row are working correctly.

 

Thank you,

 

Erick

v-chuncz-msft
Community Support

@ERDIAZ 

 

A multi-value parameter cannot include null values. When deselecting option "Allow blank value ("")", Report Builder shows error "Please enter a value for the parameter 'XXX'. The parameter cannot be blank." and Power BI Service shows error mentioned in post above. It did well in my tests.

ERDIAZ
Regular Visitor

@v-chuncz-msft,

 

This is not a multi-select value, as you mentioned Report Builder will give an error. These parameters do not allow multiple values and do not allow blank values (only the allow null value option is checked):

 

Report Parameter Properties - Division.jpg

 

I'm not doing anything that Report Builder wouldn't allow.

 

Thank you,

 

Erick

v-chuncz-msft
Community Support

@ERDIAZ 

 

That shows error in Report Builder as well. You may need to include null value in available values.

vchunczmsft_0-1633668756427.png

 

ERDIAZ
Regular Visitor

@v-chuncz-msft,

 

You are correct, it's been a long time since I created this report. I do have in the queries for the parameters:

 

SELECT
'' AS label,
NULL AS value
UNION
...

 

That plus the "Allow null value" checkbox allows the report to run successfully in Report Builder.

 

Now the question is, why do the report behaves differently on the Power BI service after publishing it?

 

Thank you,

 

Erick

v-chuncz-msft
Community Support

@ERDIAZ 

 

Use white space (' ') instead of empty string ('') as a label.