Forum Discussion
Helper IIIFilter passed by URL not respected when exporting Power BI report to pdf
- I would suggest having the filter that could be entered might be the way to get it working going forward.
Hi JDBOS ,
As mentioned in the article, the URL filters is not supported when exporting to PDF currently. Also, based on my research, I have found other considerations that URL filters are supported in some embedding scenarios and not in others:
- Embedding a report in a secure portal or website is supported.
- URL filters are supported in Power BI Embedded.
- Query string filtering doesn't work with Publish to web or Export to PDF.
- Embed with report web part in SharePoint Online doesn't support URL filters.
- Teams doesn't allow specifying a URL.
So if you want to use filter to export, maybe you could filter in the report in advance then export to pdf instead of using URL filters.
For more information about URL filter, please refer the microsoft document that could hope to help you: URL filters
Best Regards,
Yingjie LiIf this post helps then please consider Accept it as the solution to help the other members find it more quickly.
Found a work around for this that I've recently implemented in one of my reports.
The query string parameter filter I'm using is to filter a report based on [client name] and I only need one client selected for a report print out. I added the following measure:
Client Filter = IF(HASONEVALUE(Data[Client Name]),SELECTEDVALUE(Data[Client Name])=FIRSTNONBLANK(Data[Client Name],1),0). I added a slicer on the page with [client name] in the field well. I then added the created Client Filter measure to the slicer visual filter. Applied the filter for Client Filter is not 0. I updated the slicer to single selection (I'm using the chiclet slicer visual and chose force selection option). Then the trick is to have the filter exposed and layered behind another visual, that will be hidden to the user and non-actionable. Then sync the slicer to the rest of the pages in the report (mine has 20+ because its a deliverable to the client) and this will keep the applied Client Filter on the slicer and those can be hidden on the rest of the pages. But, the slicer needs to be visible on the first page, just blended into the canvas background or layered behind other visuals so the user doesn't know.
BerryBIAAdvocate I
are you saying that you completed these steps and your export PDF/PPTX held the filters shown in the slicer, which is the same "client" as shown in the Query String filter ?
Correct. I have a "landing page" for the users to select the client and query string URL will be attached to the coverage data (insurance) we have on them. The user can click on the coverage link and be directed to the coverage report filtered for the selected client. Export using the steps I outlined above holds the filter selection. Screenshots below.
Landing page
filter coming from query string parameter
filter on hidden slicer visual. The filter on this visual for "is not 0" manufactures a single select
Screenshot of export to PPT
- BerryBIA
I also built a Landing page concept..interesting that 2 people had to go down this road.
Im having one issue:
I updated the slicer to single selection (I'm using the chiclet slicer visual and chose force selection option).
Where is the Force Selection Option ?
I found the Chiclet slicer you used in the Marketplace...just in case someone ends up here. Its the only one with a Force Selection option. I couldnt get any other slicer to work that was in the default installation of PBI desktop.