Forum Discussion
Helper IISlicer doesn't work properly
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.
Super User1) 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] )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.