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

Register now to learn Fabric in free live sessions led by the best Microsoft experts. From Apr 16 to May 9, in English and Spanish.

Reply
hibarrbm
Helper I
Helper I

Token Comma Expected Error

Hi,

 

I'm receiving the "Token Comma Expected" error for script below.

 

= CALCULATE ( VAR TotalSalePrice = CALCULATE ( SUMX ( 'ODS_OWNER FACT_ORDER_LINE', IF ( 'ODS_OWNER FACT_ORDER_LINE'[ORDER_LINE_FLG] = 1, 0, 'ODS_OWNER FACT_ORDER_LINE'[TOTAL_SALE_PRICE] ) ) ) RETURN COALESCE ( TotalSalePrice, 0 ) )

 

Any ideas on how to resolve?

8 REPLIES 8
Anonymous
Not applicable

[Your Measure] =
CALCULATE(
    0 + SUM ( 'ODS_OWNER FACT_ORDER_LINE'[TOTAL_SALE_PRICE] ),
    KEEPFILTERS( 'ODS_OWNER FACT_ORDER_LINE'[ORDER_LINE_FLG] <> 1 )
)

Your expression is correct. If you have any problems with a formula and syntax, use www.daxformatter.com. I've checked it and it's OK. But your formula is not only unnecessary complex. It's also slower than it could be. The version above is MUCH faster.

THis was the original SQL statement:

 

  Sum( case when ODS_OWNER.FACT_ORDER_LINE.ORDER_STATUS_KEY in(25,133) then (

            case when (DECODE(BITAND(ODS_OWNER.FACT_ORDER_LINE.ORDER_LINE_FLG,  POWER(2 , 0)),POWER(2 , 0), '1', '0')) = 1 then 0

else ODS_OWNER.FACT_ORDER_LINE.TOTAL_SALE_PRICE

Thank you daxer! this worked perfectly.

 

I also need to add an extra filter to the statement, i also need to only apply to order status key that = 25 or 133

 

Does this work:

 

CALCULATE (

    0 + SUM ( 'ODS_OWNER FACT_ORDER_LINE' [TOTAL_SALE_PRICE]),

    KEEPFILTERS( 'ODS_OWNER FACT_ORDER_LINE' [ORDER_STATUS_KEY] = (25,133)).

    KEEPFILTERS( 'ODS_OWNER FACT_ORDER_LINE' [ORDER_LINE_FLG] <>1).

)

 

 

Thanks,

Hugo

 

Anonymous
Not applicable

// I'd shorten the name of the table
// ODS_OWNER FACT_ORDER_LINE. If you
// can shorten the names of the columns
// - even better.

[Your Measure] =
CALCULATE(
    0 + SUM (
        'ODS_OWNER FACT_ORDER_LINE'[TOTAL_SALE_PRICE] 
    ),
    KEEPFILTERS(
        'ODS_OWNER FACT_ORDER_LINE'[ORDER_LINE_FLG] <> 1
    ),
    KEEPFILTERS(
        'ODS_OWNER FACT_ORDER_LINE'[ORDER_STATUS_KEY]
        IN {25, 133}
    )
)

Apologizes, this is the second filter that needs to be applied. Once i updated the formula it gave me the following error message:

 

Test Sales New = CALCULATE (
0 + SUM ( 'FACT_ORDER_LINE'[TOTAL_SALE_PRICE] ),
KEEPFILTERS ( 'FACT_ORDER_LINE'[ORDER_STATUS_KEY] <> {27,22,20,18,23,19,-2,109,110}),
KEEPFILTERS ( 'FACT_ORDER_LINE'[ORDER_LINE_FLG] <> 1 )
)

hibarrbm_0-1597462959783.png

 

 

 

Anonymous
Not applicable

You can't write
'FACT_ORDER_LINE'[ORDER_STATUS_KEY] <> {27,22,20,18,23,19,-2,109,110}
since the LHS is a scalar and the RHS is a set. When you compare objects they must be of the same type.

The correct condition is
NOT 'FACT_ORDER_LINE'[ORDER_STATUS_KEY] IN {27,22,20,18,23,19,-2,109,110}

Looks like the measure was accepted except now it returns back with zero. any idea why that is?

 

 

lbendlin
Super User
Super User

You can always use Daxformatter.com to check your code.  In this case it comes back clean

 

a =
CALCULATE (
    VAR TotalSalePrice =
        CALCULATE (
            SUMX (
                'ODS_OWNER FACT_ORDER_LINE',
                IF (
                    'ODS_OWNER FACT_ORDER_LINE'[ORDER_LINE_FLG] = 1,
                    0,
                    'ODS_OWNER FACT_ORDER_LINE'[TOTAL_SALE_PRICE]
                )
            )
        )
    RETURN
        COALESCE ( TotalSalePrice, 0 )
)

 

but the outer CALCULATE() looks suspicious.  I don't think it is required.

Helpful resources

Announcements
Microsoft Fabric Learn Together

Microsoft Fabric Learn Together

Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City

PBI_APRIL_CAROUSEL1

Power BI Monthly Update - April 2024

Check out the April 2024 Power BI update to learn about new features.

April Fabric Community Update

Fabric Community Update - April 2024

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

Top Solution Authors