Drill through that considers slicer/filter context of a parent visual

[bjnodello1]

The current drill through capability does not appear to consider an active filter/slicer value for a visual unless the dimension being filtered is included in the parent visual. I think it would be helpful if it did. For example; a table of customers subject to a slicer for specific stores should pass on both the customer and store values if these dimensions are both listed as drill through filters.

[pedroreis]

A must have feature. Power BI users after having filters applied before applying drill through do not understand that the previous filters are now unselected. Bottom line we need to make end user experience a positive one, so this is absolutely required, otherwise the feature itself is useless.

[nithin9]

This is a must have.

[pbiideas1]

The current implementation of drillthrough is very incomplete i.e. IMHO basically broken/not usable. It should not have been released in it's current state because it makes it very easy for users to be misled / see the wrong data. Slicer selections from the summary page don't seem to be carried through to the details page. So you can either use slicers or drillthrough. But not both together in a report. Because if you use both together, the drill through doesn't show you what you intuitively expect to see. Or worse still the user does not realise the slicer selections are missing and so gets a completely different/wrong/misleading set of values.

[matthewlingard]

It would be great if we can get an update from the PowerBI team on this request. I agree with ALL the comments below especially cbaillis that this feature is basically half built and could create major issues with end users. Please prioritize this as super urgent.

[Antonio_Chan]

Hi relatively new to PBI. Ditto to all the aforementioned points particularly about having working slicer and filters elements not part of the parent report. In my case, a matrix report that also allow users to select different row/column level of details. One addition feature request is to consider having a working drill through target page report with data supported by one set of table/models that are different from the parent page report source tables, as long as the "drill through filters" or fields listed on the target page can be explicitly "matched" or defined a filter relationship from the parent to the target page report. For example, the parent page report is a high-level summarized (by account) P&L with data come from a financial ledger table, while the target drill through page report reflects detailed information (like account, cost center, detail description, other statistical fields and etc) from a journal line table. In a typical ERS, financial data from the journal line table are posted and aggregated to the ledger table at the account level. In defining the drill through filters for the target page, one should be able to explicitly define the account field listed in the ledger table is matched with the account field listed in the journal line, cost center from ledger is matched with cost center from journal line and etc. This way, drill through to another page can effectively provide a new way of viewing different type of related detail information from tables other than those tables supporting the parent page report.

[anmol_ganju]

We need a date range that will send the customer to differnet page with the exact date range.

[pbid_cd]

'+1 If someone is using the date ranges and is trying to drill through on e.g. customers category to see a volume of sales - it is a necessary feature.

[fshirokov]

'+1, my customers need this

[matthewlingard]

I was hoping that the December release would have fixed this major flaw. we desperately need a fix for the Drillthrough feature. We need the full context of the report including all filters and slicers to be passed to the target report. BTW, I believe this feature should be called Drillacross not Drill through, but anyway.

[tin_dang]

This is super important & urgent in term of analytical story designed in Power BI and should be basic feature of any analytics tool. Please prioritize this first than any other features.