Related Slicers in DirectQuery Mode

[sophie63]

Hi all,

Is there a difference in the use of slicers between the Import and the DirectQquery Mode? To me it seems that when using Import mode i can have related slicers (say I choose a country in the first slicer, in the second one i will have only the brands we are selling in  this country) whereas it's not working in the DirectQuery mode (all brands in all country appearing, despite the fact that I chose a country).

Does anyone have a clue?

[Anonymous]

Hi @sophie63,

I am not able to reproduce your issue, based on my test, related slicers works as expected when I connect to SQL Server database using import mode or DirectQuery mode.

What is the data source in your scenario? Could you please post table structure and sample data in  your tables for us to analyze?

Thanks,
Lydia Zhang

[sophie63 · Accepted solution]

@Anonymous

Actually I solved my issue, it had absolutely no links with the DirectQuery mode. It's just that I was taking two fields from different tables and in that case the cascading slicer does not work. So I did a RELATED() to import in the same table the 2 fields i was interesting in for the filter 🙂