Show empty table if filter/slicer not selected? Or limit results?

[Anonymous]

Hi guys,

I'm getting these nice looking tables/error messages and was wondering whether there's a way to either not show anything until a filter/slicer is selected or limit the results to less than 1 million/thousand/100 results or something to avoid the error? Thanks!

[v-yulgu-msft]

Hi @Anonymous,

It is not supported to hide/show a visual based on slicer selection. Such an error prompted because the Maximum number of rows returned in a DAX query is limited to 1 million rows by default. To increase the upper limit, you could specify the  MaxIntermediateRowSize configuration setting in the msmdsrv.ini configuration file.  Reference: DAX Properties

Best regards,

Yuliana Gu

[Anonymous]

Thanks v-yulgu-msft,

I just want to show an empty table if no slicers/filters are selected.

Partially to avoid getting the error, but also because it's only going to show a lot of information which is irellevant until filters are selected, so would be nice to be able to say "here's an empty table, but if you select a filter/slicer, or you click on anything in this other table which will also work as a filter, then I'll show you some data"!

[Anonymous]

You could try using HASONEFILTER in a measure to hide visuals until a filter / table column is clicked.

If in your top level table you would click on column A to filter all other visuals including your next level table.

Create a new measure

FILTERMEASURE = IF(HASONEFILTER([topleveltable.columnA]),1,0)

Then, in your next level table, drag this new measure into the visual level filter and check to show only items when the value is 1.

Your next level table should then go blank. Try clicking a column A field from your top level table, this should then only show results in your next level table relating to the selection.

I have used this in a couple of scenarios and it works well and judging on your email, it should work in this case (hopefully!)

[Greg_Deckler]

The easiest thing to do would be to set your slicer value to some default and save the report that way and then you would avoid this error.

[Anonymous]

Thanks!

So no dice if using tables instead of slicers? (say 2-3 tables where some have high level information and others more detailed , and you just select a row and then get the detailed view in the other table (say 5-10 detailed rows per 1 high level row). obviously the detailed table has more rows than others, more than 1 million if no rows is selected )

[Greg_Deckler]

Hmm, maybe not. I thought that creating a bookmark and then saving the PBIX with that bookmark selected would do the trick but apparently not. Hmm...