How to create multiple parameters to be used in Po...

PowerUser3 · ‎08-06-2025

Hello all,

I am trying to set up multiple parameters inside Report Builder and I want the parameters to be optional however that is not working at the moment. I have employee name and manager name but I don't want to have to select both. and can it be dynamic to where if you select employee name first in parameter it will show manager name automatically in parameter drop down?

v-tsaipranay

Hi @PowerUser3 ,

I wanted to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.

Thank you.

v-tsaipranay

Hi @PowerUser3 ,

I wanted to follow up on our previous suggestions. We would like to hear back from you to ensure we can assist you further.

Thank you.

v-tsaipranay · ‎08-08-2025

Hi @PowerUser3 ,

Thanks for the clarification. Since you're using a Snowflake view without custom SQL, you can still achieve optional cascading parameters by configuring filters within Report Builder. First, ensure your parameters allow nulls or include an "All" option in the parameter dataset (e.g., using UNION SELECT NULL).

Then, instead of modifying the SQL, apply filters at the dataset level using expressions like =IIF(IsNothing(Parameters!EmployeeName.Value), True, Fields!EmployeeName.Value = Parameters!EmployeeName.Value) for both Employee and Manager.

For cascading behavior, set a filter on the Manager parameter dataset to respond to the selected Employee using similar logic.This setup maintains dynamic dropdowns while keeping both parameters optional, all without changing the underlying Snowflake view.

Hope this helps. Please reach out for further assistance.

Thank you.

v-tsaipranay · ‎08-07-2025

Hi @PowerUser3 ,

Thank you for reaching out to the Microsoft Fabric Community.

The guidance and links provided by @PijushRoy are useful for configuring cascading parameters in Paginated Reports, where one parameter filters another.

If you want both parameters to be optional while keeping the cascading functionality, make sure your parameter datasets allow a default or "All" option (like NULL or a custom label). In your main dataset query and cascading logic, include conditions such as:

WHERE (@Employee IS NULL OR EmployeeName = @Employee)

This method enables users to choose one, both, or neither of the parameters, while still ensuring that dynamic filtering works when a parameter is selected.

Hope this helps. Please reach out for further assistance.

Thank you.