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

Enhance your career with this limited time 50% discount on Fabric and Power BI exams. Ends August 31st. Request your voucher.

Reply
ArchStanton
Impactful Individual
Impactful Individual

Same measure 2 different values

Hi,

I thought I had fixed this but the problem still remains.

Can anyone explain why a simple measure like this can be correct yesterday and show a value of '1' today?

YTD Closed Cases 3 = CALCULATE(
    TOTALYTD(COUNT('Cases'[Case Number]),
        'Cases'[Resolution Date],"31/03"),
            'Cases'[statecode] = "Resolved")

Yesterday:

ArchStanton_0-1738158458628.png

 

Today:

ArchStanton_1-1738158511477.png

I cannot share my pbix file because of confidential data.

Has anyone ever seen anything like this? 
I'm at a loss as to what has happened.

 

Thanks,

I've spoken to out IT department and nothing happened overnight from a Dynamics System perspective.

Regarding the images above - the measure was added to a clean blank page with no filters

1 ACCEPTED SOLUTION

Thank you for replying.

The issue was a 'human error' incident - someone had entered a future Resolution date (29/07/2025) and that screwed everything up  - my 24/25 FY ends 31st March and Jul 2025 is FY 25/26

View solution in original post

5 REPLIES 5
Bibiano_Geraldo
Super User
Super User

Hi @ArchStanton ,
if it worked yesterday and now returns 1, something in your data, filters, or model might have changed.

try to double check your slicers, filter pane and so on.

Its complicated to say what is happening whitout the sample data.
or try to filter like this to debbug:

YTD Closed Cases 3 = CALCULATE(
    TOTALYTD(COUNT('Cases'[Case Number]),
        'Cases'[Resolution Date],"31/03"),
    FILTER(ALL('Cases'), 'Cases'[statecode] = "Resolved")
)

Thank you for replying.

The issue was a 'human error' incident - someone had entered a future Resolution date (29/07/2025) and that screwed everything up  - my 24/25 FY ends 31st March and Jul 2025 is FY 25/26

Hi @ArchStanton ,

Happy you find the problem, please consider to accept the relevant reply as solution to close the tread.

 

Thank you

Greg_Deckler
Community Champion
Community Champion

@ArchStanton Well, it's possible that a refresh partially failed I suppose. Is this an import model with nightly refreshes? If so, I would first start with checking your tables to see if all the data is there that should be. 

 

Failing that, I would recode your DAX measure so that you can actually troubleshoot what is going on, maybe something like:

YTD Closed Cases 4 = 
  VAR __Today = TODAY()
  VAR __MinDate = DATE( YEAR( __Today ) - 1, 3, 31 )
  VAR __Table = FILTER( 'Cases', [statecode] = "Resolved" && [Resolution Date] > __MinDate )
  VAR __Result = COUNTROWS( __Table )
RETURN
  __Result


Follow on LinkedIn
@ me in replies or I'll lose your thread!!!
Instead of a Kudo, please vote for this idea
Become an expert!: Enterprise DNA
External Tools: MSHGQM
YouTube Channel!: Microsoft Hates Greg
Latest book!:
DAX For Humans

DAX is easy, CALCULATE makes DAX hard...

Thank you for the troubleshooting example, its something I'm going to refer to in future.

 

This current issue however turned out to be a 'human error' incident - someone had entered a future Resolution date (29/07/2025) and that screwed everything up  - my 24/25 FY ends 31st March and Jul 2025 is FY 25/26

Helpful resources

Announcements
July 2025 community update carousel

Fabric Community Update - July 2025

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

July PBI25 Carousel

Power BI Monthly Update - July 2025

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

Top Kudoed Authors