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
We intend to use drillthrough feature to enahce the user experience of our reports. Rather than having a user re-set the slicers each time they want to navigate to a new report (time which these reports are supposed to be saving the user......), this drillthrough feature will allow SEAMLESS switching between reports with the same filters.
Currently our users are VERY CONFUSED at the functionality provided in the half-baked drillthrough in the current version of Power BI.
RE: Drillthrough and slicer conflict resolution
Faced the same issue when I was working with Power BI...
RE: Drillthrough and slicer conflict resolution
drillthrough feature is half-baked without this linkage - M$, how did you intend for drillthrough pages to function autonomously if you don't give end users a slicer to choose the value driving the drillthough page? Did you just assume that people would always return to previously pages and then drill back in to the drillthrough page? Having communication between the drillthrough element and page slicers on the drillthrough page seems like a pretty easy to identify critical use case for making this functionality work in the real world. I love Power BI, but honestly I wonder what your UX people are thinking half the time.
RE: Drillthrough and slicer conflict resolution
Really need this feature.
For example, we have 2 pages - overview and details by product. Second page contains slicer "Product". If a user drills from overview page to detailed, he or she will not be able to select another product on this page using the slicer. So now we disabled drilldown feature. Hope you'll provide some solution!
RE: Drillthrough and slicer conflict resolution
The Drillthrough should consider all the filter context applied on a visual, but it is ignoring the page/slicer context.
This should be solved as a bug.
RE: Drillthrough and slicer conflict resolution
Agree this seems like a bug to me as well. Drillthrough filters in the filter pane should also reflect and be applied to any slicers.
Drillthrough Example: I drillthrough to "Yes" values on a field on a new page. That page includes a slicer for that field. The slicer should reflect "Yes", not "All".
RE: Drillthrough and slicer conflict resolution
Really surprised this is considered by design - its a bug.
If a drill through page has a slicer on that page, then whether that slicer is in drill down mode or list mode the value of the slicer should be set to the value of the data being passed to it.
RE: Drillthrough and slicer conflict resolution
This is confusing. If there's one possible value in a dropdown slicer, then show that one value, instead of the very counter-intuitive 'ALL". This isn't hard.
RE: Drillthrough and slicer conflict resolution
I actually think this is a bug. Why would you want to drill through without applying the filters/selectors that are relevant to the item you are drilling from. It appears that only the native PBI filters are applied