How to power drill through filters from a list type slicer

[Anonymous]

I have two pages in my report:

1. A page on which the user selects a customer account from a list type slicer

2. A second page whereon the user can see displayed various data attributes and visualizations for the selected customer

Issue:  After adding the customer account field as a drill through filter on the target page, I would expect to see "Drillthrough > Drillthrough destination page" when right-clicking on the customer in the list type slicer.  However, that is not happening.  The only option displayed on the right-click menu is "Show data".

Notes: 

A.  The Customer account number field used in the slicer is indeed the same field (from the same table) that I am using as my drill through field on the target page.

B.   I have successfully set up drill through from a pie chart visualization to a drill through target page.

Questions: 

a.  Is it not possible to use a list type slicer as the point of origin for drill through?

b.  If it IS indeed possible to use a list type slicer as the point of origin for drill through, what might I be doing wrong?

[v-yulgu-msft]

Hi @Anonymous,

No. It is not possible to use a list type slicer as the point of origin for drill through. 

If you want the DrillThrough feature, you can add customer account field to table visual instead. Alternatively, to still use the slicer to filter, you can enable the "Sync Slicers" between pages. When you choose a value in slicer on page1, you should manually jump to page2, then, data on page2 will be filtered based on the selected item.

Best regards,

Yuliana Gu

[Anonymous]

Thanks for the reply and for confirming I'm not crazy, Yuliana.  

The trouble with using a visualization for customer is that one sales rep may have hundreds of customers, so selecting a customer from a visualization could be physically challenging.  Maybe if I limit the visualization to a "top N" type visualization, it will become more do-able.  

And I'm aware of the "Sync Slicers" functionality and have played with it successfully on some reports.  The DAX selectedvalue() function is also useful on the target page.  

Thanks again for your help...

Greg