Forum Discussion

lcd's avatar
lcd
Frequent Visitor
9 years ago
Solved

TOTALYTD with 4 parameters

Hi, I'm a newby in powerbi and DAX. I have a measure that WORKS FINE but it has more parameters than it should have.

My measure is:

TOTALYTD(sum(GASTOS[IMPORTE]);GASTOS[FECHA];YEAR(GASTOS[FECHA]) = YEAR(TODAY());GASTOS[FASE]="100")

 

The  DAX reference for TOTALYTD is:

TOTALYTD(<expression>,<dates>[,<filter>][,<year_end_date>]) 

and only let to use ONE FILTER.

What I don't understand is WHY the function works fine with 2 filters:

YEAR(GASTOS[FECHA]) = YEAR(TODAY());GASTOS[FASE]="100"

 

Thanks in advace

 

 

  • lcd

     

    The fourth argument to TotalYTD is not a filter at all. It is a string specifying a year end date in order to calculate TotalYTD for fiscal year instead of calendar year. So we should not use another filter for the fourth argument. However, when you specify a filter condition, the intellisense signals that it is an error, but DAX engine is more tolerant during execution time which doesn’t sound like a good idea as it confused you. Power BI Team will file an internal bug to consider rejecting such expressions by the DAX engine. Thanks for reporting this.

     

    Best Regards,

    Herbert

2 Replies

  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi lcd

    I can reproduce your issue, I will report this issue internally and post back once I get any updates.

    Thanks,
    Lydia Zhang

  • v-haibl-msft's avatar
    v-haibl-msft
    Icon for Microsoft Employee rankMicrosoft Employee

    lcd

     

    The fourth argument to TotalYTD is not a filter at all. It is a string specifying a year end date in order to calculate TotalYTD for fiscal year instead of calendar year. So we should not use another filter for the fourth argument. However, when you specify a filter condition, the intellisense signals that it is an error, but DAX engine is more tolerant during execution time which doesn’t sound like a good idea as it confused you. Power BI Team will file an internal bug to consider rejecting such expressions by the DAX engine. Thanks for reporting this.

     

    Best Regards,

    Herbert