Peter Ivers on 04 Oct 2017 19:50:58
Make a drillthrough look for any slicers on the page with the same field and set them to the drillthough value.
Lets say your target is a page all about a widget with a widget slicer. An end user might slice widget A on that page. Later the user goes to another products page and sees widget B in the list, and drills through to the Widget B page. It will come up blank as the drillthrough filter is B, but the page is sliced to A, and there is no widget that is both A and B.
This is caused because the drillthrough filter and slicer are ANDed and the slicer may be set to a previous value by an end user, so zero rows are returned.
- Comments (19)
RE: Drillthrough and slicer conflict resolution
More than 6 years passed already, meanwhile this basic functionality is still an idea...
RE: Drillthrough and slicer conflict resolution
Like others have said - need slicers on target page to be synced with drill through fields. As soon as a user drills through on a target page from a list of values on a source page, they find it inconvenient to have to go back to the source page just so that they can select a second value to drill through. The target page for the drill through needs to support slicers for the same field.
RE: Drillthrough and slicer conflict resolution
So simple and still Microsoft won't do it...
RE: Drillthrough and slicer conflict resolution
I'm amazed this idea never has more traction whenever I check. Almost every time I make a report, a client wants drillthrough, and then the ability to change the sliced value on the drillthrough page. And I always have to disappoint and say that the two elements don't sync up. It makes me wonder if there's an alternate design path that I'm unaware of that the rest of the world is using 😂.
RE: Drillthrough and slicer conflict resolution
We are also waiting for this issue to fix, which will help us in performance
RE: Drillthrough and slicer conflict resolution
this would really help, the idea of creating a second page is ok, but not good. can you please fix it?
RE: Drillthrough and slicer conflict resolution
This would be really useful - it does seem like a bug at the moment. Please fix!
RE: Drillthrough and slicer conflict resolution
For those struggling with this we have a workaround that is by no means a solutions - and a potential maintenance headaches (as it involves multiple copies of the same things)
But what we did was create two pages - one that would only be used via drilled through, and one that has a splitter on that field but no drill through. The drill through one is hidden so as to not confuse the users too much. It's not great from a maintenance point of view but vastly improved the user experience.
Trying to have splitter and drill through on same field just doesn't work I Power BI. To the point where they really should throw up an error when you try (or FIX IT !!!)
RE: Drillthrough and slicer conflict resolution
This feature would help my work immensely.
RE: Drillthrough and slicer conflict resolution
This feature would not only ease my work, but also add great value to the product. Looking forward to a fix.