Forum Discussion
Slicer doesn't work properly
Hello, I have 3 tables:
These tables represent many to many relathionships by using bridge table "RegionalCalendar". I have a slicer "Year" From table "TimeDim2" and when I put a value in a slicer, table "cps_sfdc_history" is not filtered.
*I tried Cross filter direction both, but the behaviour of slicer became weird..
The key for cps_sfdc_cases_history" is CaseCreatedDate and for RegionalCalendars table is Date. So I expect when I filter by Year 2024, I will see all cases from history table which have created date in year 2024, but instead of it, I see all cases.
1) Create a proper Date table with unique dates
A classic calendar table: one row per day.
2) In the fact table, create a date-only column
If CaseCreatedDate is datetime:
CaseCreatedDate_Date = DATEVALUE ( cps_sfdc_cases_history[CaseCreatedDate] )3) Relate Date table directly to the fact (1:* , single direction)Date[Date] (1) → Fact[CaseCreatedDate_Date] (*)
Now your Year slicer will filter the fact reliably.
4) Keep “RegionalCalendar” out of the date-filter path (if it’s per-region)
If RegionalCalendar is “Date x Region” (multiple rows per date), don’t use it as the bridge between Date and Fact.
Instead:Use a separate Region dimension (if you need region filtering), or
Use RegionalCalendar only for region-specific attributes, not as the primary date connector.
3 Replies
1) Create a proper Date table with unique dates
A classic calendar table: one row per day.
2) In the fact table, create a date-only column
If CaseCreatedDate is datetime:
CaseCreatedDate_Date = DATEVALUE ( cps_sfdc_cases_history[CaseCreatedDate] )3) Relate Date table directly to the fact (1:* , single direction)Date[Date] (1) → Fact[CaseCreatedDate_Date] (*)
Now your Year slicer will filter the fact reliably.
4) Keep “RegionalCalendar” out of the date-filter path (if it’s per-region)
If RegionalCalendar is “Date x Region” (multiple rows per date), don’t use it as the bridge between Date and Fact.
Instead:Use a separate Region dimension (if you need region filtering), or
Use RegionalCalendar only for region-specific attributes, not as the primary date connector.
Hi alks_skla_f
Thank you for submitting your question to the Microsoft Fabric Community Forum, and thanks to cengizhanarslan for offering helpful suggestions.
Could you let us know if the suggested solution resolved your issue? If it's still pending, please let us know any further details so we can help.
Best regards,
Community Support Team.Hi alks_skla_f
We have not received a response from you regarding the query and were following up to check if you had the opportunity to review the information provided. Please feel free to contact us if you have any further questions.
Thank You.
