This is best Fabric, Power BI, SQL and AI community event. How do we know? The last event sold out! Save €200 with code FABCMTY200.
Register nowA new Data Days event is coming soon! This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. Don't miss out.
There is SQL in each table's query editor. DIM_Academic_Year is being limited by Academic_Year_Current_Year_Desc 0 to -10, so dim_date and the FACT are being limited to datas in the last ten academic years. Each table is LEFT JOINED onto the table to its left.
I think I understand that by keeping the cross-filtering on as bi-directional in my model, and having LEFT JOINS across the tables, DIM_Date is being filtered by the FACT to only display dates from the FACT table, but what I don't understand is why that isn't the case for the date range slicer. Why does the date range slicer have 'access' to all dates, but the table doesn't? Is this hidden behaviour of the native slicer visual I'm unaware of?
Many thanks for any help offered.
Solved! Go to Solution.
Hi @Anonymous ,
Be aware that the slicer altough is a visualization has any other works in a different way than a chart or a table, certain filterings cannot be applied to the slicer and also depending on the type of data you place on the slicer you can have different results.
In the case of date be aware, that Power BI, can be using the auto-date time feature meaning that all date columns will be "changed to a calendar" meaning showing all dates from the frist on your model to the last one.
Can you check if on your file you have the auto date-time turn on?
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsHi @Anonymous ,
Believe your issue is related with the fact that you are using bidirectionality on both relationship you have on your model so the information get's filtered out in both ways and you may filter out information by mistake.
Try to make the relationship filter to single side and check if everything works properly.
If this does not help can you please share a mockup data or sample of your PBIX file. You can use a onedrive, google drive, we transfer or similar link to upload your files.
If the information is sensitive please share it trough private message.
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsThanks for the reply @MFelix ,
If that was true (and changing the filter direction to one-way does solve a different issue I had in the report), it'd be true for both the slicer and the table surely? As it is, the bi-directional relationship seems to be affecting the table but not the slicer, or the slicer would only show up to 13/12/21 as well. My confusion is about why the slicer isn't behaving the same as the table, as if the slicer can ignore the relationship in the model and call on the full range of dates. If I change the slicer visual to a table or card, it then only shows dates up to the 13/12/21. Changing it back to a slicer adds in more dates. Is as if there's hidden behaviour in the slicer.
Any ideas?
I'll try mock up and upload a model all the same.
Hi @Anonymous ,
Be aware that the slicer altough is a visualization has any other works in a different way than a chart or a table, certain filterings cannot be applied to the slicer and also depending on the type of data you place on the slicer you can have different results.
In the case of date be aware, that Power BI, can be using the auto-date time feature meaning that all date columns will be "changed to a calendar" meaning showing all dates from the frist on your model to the last one.
Can you check if on your file you have the auto date-time turn on?
Regards
Miguel Félix
Proud to be a Super User!
Check out my blog: Power BI em PortuguêsCheck out the May 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 30 | |
| 28 | |
| 23 | |
| 19 | |
| 17 |
| User | Count |
|---|---|
| 49 | |
| 47 | |
| 41 | |
| 21 | |
| 19 |