Forum Discussion

Damian911's avatar
Damian911
Frequent Visitor
2 years ago
Solved

Average - Distinct

Spool =
CALCULATE(
    AVERAGE('AllInvoiceDetails'[Quantity]),
    'Product'[ProductGroup] = { "Spool" }
)
 
I have the above formula but it is not working.
In the Product Group there may be 2 values with "Spool"
I think I just need to add a Distinct but I keep getting errors.
 
Where there is 2, I am getting double the number.
 
Can someone tell me how to add a Distinct.
 
Thanks
 
 
 
  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi Damian911 ,

    I am glad to help you.
    Jihwan_Kim ,Thank you very much for your help with this case!
    I've come up with another solution that I'd like to share.

    Based on your description, I think you can try to change the DAX code to this:

     

    Spool = 
    CALCULATE(
        AVERAGE('AllInvoiceDetails'[Quantity]),
        FILTER(
            'Product',
            'Product'[ProductGroup] = "Spool"
        )
    )

     

    I created the following test data as you described it.

    It is recommended to use the filter function in the calculate function to filter out a separate range for calculation (from the Product table to filter out ProductGroup = "Spool" rows of data), then only ProductGroup for the "Spool" rows will be used in the previous average method. (Requires a relationship between the tables.)

    Using the filter function, it is possible to individually restrict a calculation range (creating a new table), which does not affect the other dax expressions of the model.

    Here's what happens when no relationship is created between tables:

    The results for both are incorrect.
    When a relationship is established between two tables:

     



     

    The above code not only calculates the average value in the "spool" according to the filter range, but also calculates the duplicate ID (value 2) records only once.
    The above measure using the filter function is correct, and correspondingly, the following expression does not change the filter range before and after the relationship is created.

     

    I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.

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

2 Replies

  • Hi,

    Please share your sample pbix file's link.

    Or, please try something like below whether it suits your requirement.

     

    Spool =
    CALCULATE (
        AVERAGE ( 'AllInvoiceDetails'[Quantity] ),
        'Product'[ProductGroup] IN { "Spool" }
    )
    
  • Anonymous's avatar
    Anonymous
    Not applicable

    Hi Damian911 ,

    I am glad to help you.
    Jihwan_Kim ,Thank you very much for your help with this case!
    I've come up with another solution that I'd like to share.

    Based on your description, I think you can try to change the DAX code to this:

     

    Spool = 
    CALCULATE(
        AVERAGE('AllInvoiceDetails'[Quantity]),
        FILTER(
            'Product',
            'Product'[ProductGroup] = "Spool"
        )
    )

     

    I created the following test data as you described it.

    It is recommended to use the filter function in the calculate function to filter out a separate range for calculation (from the Product table to filter out ProductGroup = "Spool" rows of data), then only ProductGroup for the "Spool" rows will be used in the previous average method. (Requires a relationship between the tables.)

    Using the filter function, it is possible to individually restrict a calculation range (creating a new table), which does not affect the other dax expressions of the model.

    Here's what happens when no relationship is created between tables:

    The results for both are incorrect.
    When a relationship is established between two tables:

     



     

    The above code not only calculates the average value in the "spool" according to the filter range, but also calculates the duplicate ID (value 2) records only once.
    The above measure using the filter function is correct, and correspondingly, the following expression does not change the filter range before and after the relationship is created.

     

    I hope my suggestions give you good ideas, if you have any more questions, please clarify in a follow-up reply.

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