Report Builder - Required Unchecked in Desktop App, but Required after Publishing

[mmsherer]

Hey Ya'll. 

I've been following these two tutorials: 

https://www.youtube.com/watch?v=9qgFDkpfGPc

https://www.youtube.com/watch?v=XSIbRNXGgPQ

But I cannot for the life of me figure out this issue. In PowerBI Report Builder I have my parameters set as not required, but when I publish to service they are required. I have a table connected via sql server, and the parameters created by a combination of the above (mostly the second). Here are my settings: 

I've tried redoing multiple times, the only thing I still have to try is the default value? Maybe because I don't have one it's making me pick something? 

Thanks!!

[v-sgandrathi]

Hi @mmsherer,

Following up to check whether you got a chance to review the suggestions given. If the issue still persists please let us know. Glad to help. 

Thank you.

[mmsherer]

Wonderful! Thank you for the suggestion - I will try that 🙂

[v-priyankata]

Hi @mmsherer 

Thank you for reaching out to the Microsoft Fabric Forum Community.

I hope the information provided was helpful. i hope you have tried that, please don't hesitate to reach out to the community if you have any other issues.

[v-priyankata · Accepted solution]

Hi @mmsherer 

Thank you for reaching out to the Microsoft Fabric Forum Community.

Your thought is likely correct. When a parameter is used in the dataset query, Power BI Service still expects a value to be passed when the report runs. If no default value is set, the Service will prompt you to choose one before executing the report.

One thing you could try is setting a default value for the parameter so the report can run without requiring a selection each time. Another option, if the parameter is meant to be optional, is to adjust the dataset query to handle NULL values (ex : WHERE (@Parameter IS NULL OR Column = @Parameter) ). This allows the report to run even when no value is selected.

If there are any deviations from your expectation please let us know, we are happy to address. 

Thanks.

[mmsherer]

Yes! It was a combination of things. The default parameters was one part, but I think for anyone viewing this later, I also had not set up the parameter queries correctly, in the Query Designer page. Lessons learned on DAX. 🙂 Thank you all!