Forum Discussion
Paginated Report
Hi LaurenzR , hope you are doing great. May we know if your issue is solved or if you are still experiencing difficulties. Please share the details as it will help the community, especially others with similar issues.
Hi v-hashadapu, unfortunately i did not solve the problem. Your tip with the Treatas statement sadly did not work, because Treatas need a column input an not a list of values. i tried to get the parameter values as a column by using Row(), but this did not work either. If it does not work at the next try i am just going to make two files. One with the Customer filter and the other without it.
Hi LaurenzR , thanks for the update. Please do keep us posted with the results, that may help others with similar issues.
Hi LaurenzR,
You are correct, the previous TREATAS example won't work directly because paginated report multi-value parameters aren't automatically available as a table expression for TREATAS(). Also, hiding a tablix doesn't stop its dataset from running, so both queries are sent to the semantic model.
The cleanest solutions are:
- Create two separate paginated reports:
- one with customer filtering
- one without the customer parameter
This prevents the large expanded filter that RSCustomDaxFilter generates when all customers are selected or, redesign the dataset logic so filtering occurs upstream (like in the semantic model or source query), rather than passing a large multi-value parameter list from Report Builder.
RSCustomDaxFilter has limitations in complex “Select All” situations because it creates a long filter statement internally, and Power BI Service/gateway limits are usually stricter than in Report Builder Desktop.
Thank you.
- Create two separate paginated reports:
