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

Prepping for a Fabric certification exam? Join us for a live prep session with exam experts to learn how to pass the exam. Register now.

Reply
sgajjar
Frequent Visitor

Issue with Measure in Table1 Breaking When Adding DateTime Column to Table2 in Power BI

Hello Power BI Community,

I am encountering an issue with a measure from Table1 when I try to use it in Table2. I have a table (Table1) with a measure that works fine, and I want to use that measure in another table (Table2) that contains multiple columns, including a DateTime column.

The Problem:

  • When I add a DateTime column to Table2, the measure from Table1 breaks, and I can no longer use the new measure in Table2.
  • The issue seems related to row context, particularly when I try to apply a filter in Table2 that involves the DateTime column.
  • If I remove or hide the DateTime column in Table2, everything works as expected, and I can use the measure from Table1 without any issues.

What I’ve Tried:

  • I've checked the relationships between the tables, and they seem fine.
  • I've tried adjusting the row context(need to use row context for RLS) context in my DAX expressions, but the issue persists when the DateTime column is present.
  • I’ve also verified that there are no circular dependencies or incorrect relationships causing this.

Questions:

  • Has anyone encountered a similar issue where adding a DateTime column to a table breaks the use of a measure from another table?
  • What could be causing this behavior, and how can I resolve the issue without removing the DateTime column?
  • Any suggestions on how to adjust the row context and filter context to make this work properly when dealing with DateTime columns?

Any help or insights would be greatly appreciated!

Thank you in advance!

 
 
 
 
1 ACCEPTED SOLUTION

Thanks, this helped. Eventually had to replace all measures with columns on existing table and had to use removefilters for datatime column. that fixed the context issue. 

View solution in original post

3 REPLIES 3
Anonymous
Not applicable

Hi,  @sgajjar 

Make sure that the DateTime column of Table2 has the correct relationship with Table1 or the date table. If you're using a separate date table, check that the two are correctly related by the date field. If Table2 filters Table1, ensure that the relationship is one-way (usually from the date table to the fact table) to prevent conflicts caused by two-way filtering.

 

How to Get Your Question Answered Quickly

Best Regards

Yongkang Hua

If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.

Akash_Varuna
Community Champion
Community Champion

Hi @sgajjar 

  • Adding a DateTime column can alter row context, breaking measures due to filter propagation.

  • The DateTime column introduces finer granularity, changing row context and impacting the measure's evaluation.

  • To resolve without removing the DateTime column, use CALCULATE with REMOVEFILTERS or aggregate the DateTime column to reduce granularity
    If this post helped please do give a kudos and accept this as a solution
    Thanks In Advance

Thanks, this helped. Eventually had to replace all measures with columns on existing table and had to use removefilters for datatime column. that fixed the context issue. 

Helpful resources

Announcements
May PBI 25 Carousel

Power BI Monthly Update - May 2025

Check out the May 2025 Power BI update to learn about new features.

May 2025 Monthly Update

Fabric Community Update - May 2025

Find out what's new and trending in the Fabric community.