retain Drillthrough filters between multiple pages

[matthias_vc]

I'm making a report with three layers:
1) Landing page (has table with multiple projects)
2) Project overview page (currently multiple buttons to go to specific details pages of that project)
3) Project Details page (e.g. project Resources, project costs,...)
I know that I can access the "Project overview" page with a drill-through from the table.
However this filter is not retained when I use any button in this project overview page to go to a details page.
e.g. If I start on page 1, I click drillthrough in the table at Project 3 I reach page 2 and show only data specific to Project 3

I click on a button to open page 3, but the filters are not kept so I go back to page 3 but the data is reverted to project 1.

I know I can use synchronised slicers, but then I lose the "drill through" option and I'm not sure whether I can make it look elegant

[matthias_vc]

Hi @some_bih I checked the videos. There was one VERY recent one but it was the other way around (trying to set a drillthrough from a Slicer (I wanted to set a slicer from a drillthrough).
However there was another video: "you will never do DRILLTHROUGH any other way in Power BI".
This used the idea of hyperlinks instead of drillthrough.
The basis there is actually okay although there are some Pro's and Con's:
PRO: You can click through using just the left mouse button from within the object itself (no need for right-clicking => drill-through => Report ...). PRO: You're essentially setting a filter for "All pages," so the filter from that point is automatically preserved (exact functionality I was looking for). CON: You're actually loading the entire report, which takes significantly longer than a regular drill-through. CON: Links open in a new tab (this could also be a PRO since it allows you to select another project more quickly). CON: The URL experience only works in Power BI Service, not on the desktop, making it harder to test. CON: The "All pages" filter is applied on top of any existing filters. It's important that no filters on the requested field are active when the report is published; otherwise, you might end up with no data (e.g., Project Name = "a" + Project Name = "b" => no result because a project name can't be two things at once). CON: You can only set a URL after the report has been published (because you need to know the link). CON: When you navlgate back to the overview, the filter is ALSO remembered, so either: The user needs to manually remove the filter, or you need to guide the user back via a button (again using a URL, this time without the filter). In this case, it's best to hide most pages. CON: The entire "page navïgation" system gets to be unusable because the filters are not added/removed properly. PRO: Since you're loading the entire report anyway, you might as well work with different small reports linked together. This allows different people to work simultaneously on different parts.

[some_bih]

Hi @matthias_vc great for something usefull for you from suggestion / link.

I hope in future there will be some feature so some kind of workround is not needed.

If this somehow resolve your issue please accept as solution so other member of community could reuse it.

[some_bih · Accepted solution]

Hi @matthias_vc I recently saw video from curbal on youtube for this. I could not go to youtube to find your exact video due to network limitation so please check youtube for curbal power bi recent videos.