I have a table that is being filterred by 2 slicers. The two slicers are connected. I want to hide the contents of the table when no selection is made.
The slicers are 'Category' and 'Sub Category' (named Service).
I have created a measure to do that and it works if no selection made in the first slicer (Category). But I want to hide the table until a selection is made in the second slicer. If I apply a similar measure for the second slicer then that doesn't hide the table.
I have attached the file in question.
The measures are 'Category Filtered' and 'Services Filtered'. If I apply 'Category Filtered' to the table, then the table is not displayed if no categories are selected. However, if I apply 'Services Filtered' to the table, the table is always displayed.
Can anyone advise please?
Thank you
Neat feature you are using here and I hope I've understood it correctly. Remove Service from the main table, but include Category. This will 'hide' the main table until something is selected in the Service slicer.
Thank you, Riny.
Yes - that works, but it's the services that I am wanting to show in the table rather than the categories!
Then I can't help you I'm afraid. Perhaps someone else.
Had another look at it. What if you put both the Category and Service 'is filtered' on the visual?
Nothing selected in Category will hide the table and the Service slider buttons.
Select a Category and the table will show all for that category and the Service slicer becomes visible.
Thank you for looking again, Riny
Yes, (I think) I've tried that also, but I don't want to show all the services in the table. I need to wait until one has been selected in the slicer and just display that.
I've tried:
Are you suggesting something different?
I've also looked at adding a button to press before the table is displayed (unhidden!) but there isn't an on_click type function for buttons.
I'm now looking at adding a 'button' via a new slicer with 'Apply' and 'Clear' and using the SELECTEDVALUE to trigger the filter. Since that field won't be in the table, I'm thinking it might work!
Thanks
I ran out of ideas. Sorry.
Yet again, I had another idea!
Create a calculated column in dimServices, called Svc, for example:
Brilliant logic! Thank you, again, Riny.
Best wishes
It took a while, but glad we figured it out.