Forum Discussion
Slicer doesn't affect matrix
Hi everyone!
I have a matrix to which i want to connect a slicer (months to select). So I connected a slicer to the matrix however even though I checked the interaction to be on filter (via Format, edit interactions), the slicer won't affect the matrix. If I hover over the filter / slicer icon of the matrix it also shows that the slicer on the months is active. If I set the filter instead by adding a filter to the matrix via filter-pane (instead of a slicer) it works.
What could be the problem?
Thanks a lot!
Apologies, I tried this again on my own computer the issue is the dat_date is marked as a date table which makes complete sense but however it is causing your problem.
What you need to do copy the code for dat_table and then remove it from your model, then stick it back in again but this time don't mark dat_date column as a date table. Then make sure dat_date is formatted as below...
This should do the trick.
Now make the relationship you were looking to make to 'betriebstag' but make sure 'betriebstag' is in the same format as dat_date.
Hopefully this should work!
5 Replies
Hi Anonymous , If your slicer won't affect your visuals/tables it is either a relationship problem or page level filter issue. Could you send an example of your relationship?
Ah maybe the reason is, that I imported a date-table instead of using the date-hirarchies of Power BI?
In this screenshot you can see the relationship between the date-table and the table I am visualising data of:
dat_date is a date as follows:
However my slicer filters not for "betriebstag", which is obviously of the same format as dat_date, but for "abrechnungsmonat", which is reffering to a month of a year:
its format is currently text.
Is this the problem? How can I solve it? It is the first time I am making use of a custom datetable...
Thanks!!
Hi, according to your relationship you should be able to filter on the table from your Date Table. If I were you I would change the format of dat_date to Date format Long Date but make sure it doesn't break your model if it is big! Give that a go see if that fixes it.
Apologies, I tried this again on my own computer the issue is the dat_date is marked as a date table which makes complete sense but however it is causing your problem.
What you need to do copy the code for dat_table and then remove it from your model, then stick it back in again but this time don't mark dat_date column as a date table. Then make sure dat_date is formatted as below...
This should do the trick.
Now make the relationship you were looking to make to 'betriebstag' but make sure 'betriebstag' is in the same format as dat_date.
Hopefully this should work!