Forum Discussion
Paginated Report - Using URL Parameters and Select ALL
Ok, after much investigation and great support from Microsoft, we found the solution and it was dead simple!
Set the paginated report up so all parameters are loaded with Default values from the dataset. And then for the URL string passed from the calling Power BI report, only reference a parameter if the user has actually selected a value from a slicer. If the user has selected no values from any slicers (eg Select All), then simply submit the default Paginated Report URL string. If a user has selected a value from a slicer, then modify the URL to include a reference to that particular parameter and its selected values.
Ok, after much investigation and great support from Microsoft, we found the solution and it was dead simple!
Set the paginated report up so all parameters are loaded with Default values from the dataset. And then for the URL string passed from the calling Power BI report, only reference a parameter if the user has actually selected a value from a slicer. If the user has selected no values from any slicers (eg Select All), then simply submit the default Paginated Report URL string. If a user has selected a value from a slicer, then modify the URL to include a reference to that particular parameter and its selected values.
Good to hear it is working after 'ALL' 😉
So we where looking a bridge too far to make it work ...
Thanks for posting back the final solution ! 🤗
Haha, I like what you did there! Thanks for your help though 🙂
It has been a big reflief to get it sorted as we really wanted the ability to offer our users fully formatted Excel and PDF extracts of their filtered data. So in our real world example, where we have 8 slicers, some with 100 values in some of them, we will only add a value to the URL if a user has specifically selected any value/s. This means in 9 times out of 10, when they just want to see all the data, that the URL will be unmodified and just that of the Paginated Report. If they select a few values, we simple include those in the URL. So much better than having to concatenate every sli er value into the URL. I am sure we tried this, but it looks like we missed it. Seems so obvious now!
On a side note, MS did actually confirm that the URL is limited to just 800 chars, beyond that it will fail. However our users would have to really go to town, selecting 30+ values from the slicers to hit this.
Mark