Skip to main content
cancel
Showing results for 
Search instead for 
Did you mean: 

Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.

Reply
dedelman_clng
Community Champion
Community Champion

slicer on fact table not affecting "running" calculated columns/measures

I have a fact table for "IT Outages" which joins to a date dimension table for "Date" on a single direction.  On this date dimension table I have made a number of calculated columns and measures to visualize the running total for "uptime" over the year (as an area graph).  I have also done measures to show the current YTD uptime as of the last refresh.

 

UT 1.png

 

 

 

 

 

 

 

 

 

 

 

 

When I add a slicer and put in the "affected system" values from the fact table, the "single point in time" measures (e.g. YTD uptime as of today) correctly recalculate/display, but the graph visual is unchanged.

 

UT 3.png

 

 

 

 

 

 

 

 

 

 

 

 

If I change the relationship to be a "both", then neither one visual works correctly (top right - YTD Outage Time).  I think this is because there is not an outage every day, so the dates that contibute to many of the columns/measures are excluded.  The measure that is correct only pulls from the fact table.

 

UT 6.png

 

 

 

 

 

 

 

 

 

 

 

 

I can post my measure/columns if that would be helpful.

 

Thanks!

David Edelman

 

 

1 ACCEPTED SOLUTION

After working on this for a while longer, I realized that I should have been using measures instead of calculated columns.  Once I changed the data used in the "values" of the line chart from a column to a measure, the filters worked correctly. 

 

The cross-filter join needs to be single-directional still in order for the graphs to pick up all of the values from the "Date" table.

View solution in original post

5 REPLIES 5
Anonymous
Not applicable

Hi @dedelman_clng,

 

Can you share us a sample file to test?

 

Regards,

Xiaoxin Sheng

A PBIX file can be found here:

 

Uptime Report with Slicer

Anonymous
Not applicable

Hi @dedelman_clng,

 

Based on test, I find the TOTALYTD function will be affect by filter, you should modify your measure which use the TOTALYTD function to ignore the filter, for example:

 

Before:
RunningUpTime = TOTALYTD(sum('Date'[UptimeMin]), 'Date'[Date])

After:
RunningUpTime = SUMX(Filter(all('Date'),[Date]>=Date(year(max([date])),1,1)&&[date]<=max([Date])),'Date'[UptimeMin])

 

 

Then modify the "cross filter direction" to both.

 

Regards,

Xiaoxin Sheng

I have tried your suggestion but the behavior is no different.  The graphs are still starting at and only taking into account those dates with a matching outage.

After working on this for a while longer, I realized that I should have been using measures instead of calculated columns.  Once I changed the data used in the "values" of the line chart from a column to a measure, the filters worked correctly. 

 

The cross-filter join needs to be single-directional still in order for the graphs to pick up all of the values from the "Date" table.

Helpful resources

Announcements
FabCon Global Hackathon Carousel

FabCon Global Hackathon

Join the Fabric FabCon Global Hackathon—running virtually through Nov 3. Open to all skill levels. $10,000 in prizes!

FabCon Atlanta 2026 carousel

FabCon Atlanta 2026

Join us at FabCon Atlanta, March 16-20, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.

Top Solution Authors