Solved: Measure is computing wrong value

ArchStanton · ‎08-31-2022

Hi,

I have a table called 'Case' in my datamodel that contains 4,392 records that were created YTD so far (after 31st Mar)

Why does the measure below compute a figure that is more than double (9,562)?

YTD New Area = CALCULATE(TOTALYTD(COUNT('Cases'[Into Area Date]),'Date'[Date],"31/03"))

FYI, the Into Area Date was created in Power Query and is formatted as a Date

Date [Date] = CALENDAR(MINX('Cases','Cases'[tpo_legacycasecreationdate]),TODAY()+[FY Days Remaining])

I can't see why this is happening, can anyone help?

Thanks,

ArchStanton · ‎08-31-2022

Thanks, but i think i've worked it out, the Into Area Date was introduced to my table recently but it has no relationship with my date table. I just connected the 2 together and now the measure works but otheres were reliant on the other relationship are broken.

Looks like the Into Area Date needs its own table

View solution in original post

PaulDBrown · ‎08-31-2022

Maybe try DISTINCTCOUNT instead of COUNT if you need distinct values?

Did I answer your question? Mark my post as a solution!
In doing so, you are also helping me. Thank you!

Proud to be a Super User!
Paul on Linkedin.

ArchStanton · ‎08-31-2022

Thanks, but i think i've worked it out, the Into Area Date was introduced to my table recently but it has no relationship with my date table. I just connected the 2 together and now the measure works but otheres were reliant on the other relationship are broken.

Looks like the Into Area Date needs its own table