Forum Discussion
Report Builder Dataflow and Paramater
I am having to pull in data from the dataflow rather than the semantic model which is fine. I have then pulled in a semantic model for the Year & Month to use as a paramater to allow the user the filter to their required month.
Everything is all set up and runs, but when I choose a desired month it is ignores this and pulls through everything.
What can I do to bind the two separate datasets together, or even an alternative option to use a calendar as a seperate dataset and parameter.
Hi SC07,
Hope you're doing well!
Here's a clear breakdown of what's happening and how to fix it. No worries, this is a very common use case in Power BI Report Builder!
--> Why your filter isn't working ?
The core problem is that Power BI Report Builder treats each dataset as completely independent. When you have your dataflow dataset and your semantic model calendar dataset, selecting a value in one doesn't automatically filter the other. The parameter you created is "linked" to the calendar dataset visually, but it's not being passed as a query filter into the dataflow dataset, so it just pulls everything.
--> Solution :
You should filter inside the dataflow dataset query. When you set up your dataflow dataset in Report Builder, you need to edit the query so it actually receives your parameter value:
- In Report Builder, right-click your dataflow dataset → Dataset Properties
- Go to the Parameters tab
- Add a parameter here (e.g. @YearMonth) and map it to your existing report parameter
- Then in the Query tab, make sure your query actually uses that parameter in a WHERE clause — something like WHERE YearMonth = @YearMonth
The key issue is that the parameter needs to be wired into the query itself, not just exist as a report-level parameter floating in space.
--> Remember that :
Report Builder datasets don't "talk" to each other automatically. Unlike Power BI Desktop where slicers filter everything, in Report Builder you have to explicitly pass parameter values into each dataset's query. Thinking of it like a stored procedure that needs its arguments passed in every time helps make this click.
Here are some useful official MS documentation if needed more information :
Filter, Group, and Sort Data (Report Builder) — Microsoft Learn
Add Dataset Filters, Data Region Filters, and Group Filters — Microsoft Learn
Report Parameters in Report Builder — Microsoft Learn
Create a Paginated Report with Power BI Dataflows — Microsoft Learn
Hope this helps. Feel free to ask me questions if needed, and don’t forget to like (kudos) & Accept as Solution if this guidance worked for you. That's motivate me to keep helping.
Best regards,
Oussama (Data Consultant & Fabric's Expert)
4 Replies
Hi SC07,
Hope you're doing well!
Here's a clear breakdown of what's happening and how to fix it. No worries, this is a very common use case in Power BI Report Builder!
--> Why your filter isn't working ?
The core problem is that Power BI Report Builder treats each dataset as completely independent. When you have your dataflow dataset and your semantic model calendar dataset, selecting a value in one doesn't automatically filter the other. The parameter you created is "linked" to the calendar dataset visually, but it's not being passed as a query filter into the dataflow dataset, so it just pulls everything.
--> Solution :
You should filter inside the dataflow dataset query. When you set up your dataflow dataset in Report Builder, you need to edit the query so it actually receives your parameter value:
- In Report Builder, right-click your dataflow dataset → Dataset Properties
- Go to the Parameters tab
- Add a parameter here (e.g. @YearMonth) and map it to your existing report parameter
- Then in the Query tab, make sure your query actually uses that parameter in a WHERE clause — something like WHERE YearMonth = @YearMonth
The key issue is that the parameter needs to be wired into the query itself, not just exist as a report-level parameter floating in space.
--> Remember that :
Report Builder datasets don't "talk" to each other automatically. Unlike Power BI Desktop where slicers filter everything, in Report Builder you have to explicitly pass parameter values into each dataset's query. Thinking of it like a stored procedure that needs its arguments passed in every time helps make this click.
Here are some useful official MS documentation if needed more information :
Filter, Group, and Sort Data (Report Builder) — Microsoft Learn
Add Dataset Filters, Data Region Filters, and Group Filters — Microsoft Learn
Report Parameters in Report Builder — Microsoft Learn
Create a Paginated Report with Power BI Dataflows — Microsoft Learn
Hope this helps. Feel free to ask me questions if needed, and don’t forget to like (kudos) & Accept as Solution if this guidance worked for you. That's motivate me to keep helping.
Best regards,
Oussama (Data Consultant & Fabric's Expert)
Hi SC07,
Thank you for reaching out to Microsoft Fabric Community.
Thank you oussamahaimoud for the prompt response.
As we haven’t heard back from you, we wanted to kindly follow up to check if the solution provided by the user's for the issue worked? or let us know if you need any further assistance.
Regards,
Community Support Team.Yes, this resolved my issue, I was able to add a year_month column in the dataset and then created a copy and removed the other columns leaving year_month and date which I then used as a paramater and filtered using the same method that you mentioned above.
Hi SC07,
Glad to hear it’s working now
Thanks for confirming the update.If you face any other issues or need help in future, feel free to post here. We will be happy to help.
Regards,
Community Support Team.
