Power BI is turning 10! Tune in for a special live episode on July 24 with behind-the-scenes stories, product evolution highlights, and a sneak peek at what’s in store for the future.
Save the dateEnhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.
Hi all,
I have been trying really hard to figure this one out but to no avail! I have experience building dashboards in the past so can't see what I'm doing that is making this happen!
I have created a relationship between the Fact and Dimension table. I have tested this in a table and it works as expected (please see relationship and table below)
However the slicers with a Year and Date field from the Calendar table will not show the range of dates as per the table (in this case, only January and May 2025 data) and is showing the entire range of the Calendar table.
I've never had this problem, I've tried resetting the filters and everything. I even created a new date dimension table to isolate the issue in case it was somehow being caused by all the other rlationships to the original Calendar table but I get the exact same problem. The Fact table is a view from a data warehouse in Fabric but I don't think that should affect anything.
Thanks in advance!
Solved! Go to Solution.
hi @cazza
You can create measures or other filters, then add it to your slicer and show only the relevant dates in scope but typical behavior is slicer filters all other page visuals, not the other way around.
Also, having a bi-direction from your date table to your fact table(s) are usually avoided because other factors from your other dimension(s) may influence or cause issues in getting the right results. I'm sure there are probably some use cases but from the hundreds of semantic models that I've created, none of them has a bi-direction to my date / calendar table.
Hope that helps!
Hi @cazza ,
we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Regards,
Chaithanya
Hi @cazza ,
we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Regards,
Chaithanya
Hi @cazza ,
we would like to follow up to see if the solution provided by the super user resolved your issue. Please let us know if you need any further assistance.
If our super user response resolved your issue, please mark it as "Accept as solution" and click "Yes" if you found it helpful.
Regards,
Chaithanya
hi @cazza
You can create measures or other filters, then add it to your slicer and show only the relevant dates in scope but typical behavior is slicer filters all other page visuals, not the other way around.
Also, having a bi-direction from your date table to your fact table(s) are usually avoided because other factors from your other dimension(s) may influence or cause issues in getting the right results. I'm sure there are probably some use cases but from the hundreds of semantic models that I've created, none of them has a bi-direction to my date / calendar table.
Hope that helps!
Hi,
I was under the impression that if I had a bideirectional filter, the Year slicer would only show the latest year, so in this case 2025. This is how I've alwasy managed to get the slicer to only show the relevant date range without restricting the date dimension itself. I might have completely misunderstood how this should work?
Hi @cazza
I'm not sure what you mean? By default, the slicers DO show all dates from your Calendar table. Your visuals gets filtered based on your slicers.
Are you saying you want your visuals to filter your slicers instead?
User | Count |
---|---|
79 | |
74 | |
44 | |
32 | |
28 |
User | Count |
---|---|
100 | |
93 | |
52 | |
50 | |
48 |