Forum Discussion
Paginated Report
Hi LaurenzR , Thank you for reaching out to the Microsoft Community Forum.
I think this is happening because when you select all customers, the paginated report generates a much larger DAX query behind the scenes, usually expanding the parameter into a big filter list. That query becomes too complex for the Analysis Services engine to execute in the Power BI Service, especially through the gateway, even though it still works in Report Builder locally.
I suggest you don’t pass All as a multi value parameter containing every customer. Instead, handle All as no filter in your dataset query, so it doesn’t inject thousands of values or redesign the parameter to reduce the number of values being passed.
Hello, thank you for the help.
I use RRSCustomDaxFilter in the Dataset as a Filter. How can i configure the Parameter / the Dataset Query, so that all Items are selected but not in the Query that gets executed(As you mentioned "All as not filter in the dataset query").
Hi LaurenzR , Thank you for reaching out to the Microsoft Community Forum.
With RSCustomDaxFilter, you shouldn’t let it run when All is selected, because that’s what expands into a huge filter. I suggest you introduce an All option in your parameter (e.g., value = “ALL”) and then make your dataset query conditional: if the parameter = “ALL”, you skip RSCustomDaxFilter entirely (no customer filter applied); otherwise, you apply RSCustomDaxFilter as you do today. In other words, All should translate to no filter in the query, not a filter containing every customer, that’s what prevents the query from becoming too complex in the Service.
Thanks for your help. I think i found a way to implement this solution into my Dax Dataset Query, but when i want to try it i get the Error: "RSCustomDaxFilter is not a valit table, variable or expression name". I have got this error also in the past but have not realy found why this happens and how to fix it
Hi LaurenzR ,
RSCustomDaxFilter isn’t an actual DAX function, it’s a placeholder that Report Builder only recognizes in its original position in the query. If you try to wrap it in IF, use it in a variable or move it around, the engine can’t resolve it and throws that error.
So, instead of making it conditional in DAX, keep RSCustomDaxFilter exactly where it is and control it through the parameter. Add an ALL option and when that’s selected, pass a blank/Nothing value to the parameter so the filter doesn’t get applied. That way All behaves like no filter, without breaking the query.