Slicer affecting the dax

[saud968]

I have the below 2 measures, further i have a calculated column - 

P1 Hour = IF(support__cw_ops_manage_case_merge[Priority] = "P1 - Critical" && support__cw_ops_manage_case_merge[Response Hour]>0 && support__cw_ops_manage_case_merge[Response Hour] <=1, "P1 - 1 hr", BLANK()) which I am using in a slicer.

Case Volume = CALCULATE(DISTINCTCOUNT(support__cw_ops_manage_case_merge[ID]), FILTER(  support__cw_ops_manage_case_merge,

         NOT(ISBLANK(support__cw_ops_manage_case_merge[RESPONSE_SLA_MINUTES]))))

P1 Case Volume =

CALCULATE(

    [Case Volume],

    FILTER(

        support__cw_ops_manage_case_merge,

        support__cw_ops_manage_case_merge[Priority]= "P1 - Critical" &&

        NOT(ISBLANK(support__cw_ops_manage_case_merge[RESPONSE_SLA_MINUTES]))

    ),

    REMOVEFILTERS(support__cw_ops_manage_case_merge[Priority])

)

As you can I select the slicer, and the case volume changes in the table visual

As you see in the images. I have tried remove filters, all, allexpect but nothing is working. Please help

@Ahmedx @Idrissshatila @amitchandak @Ritaf1983 @Fowmy 

[saud968 · Accepted solution]

This was resolved 

Response Case Volume =

CALCULATE(

    [Case Volume],  

    FILTER(

        support__cw_ops_manage_case_merge,

        support__cw_ops_manage_case_merge[RESPONSE_SLA_MINUTES] <> BLANK()

        && (

            support__cw_ops_manage_case_merge[Priority] = "P1 - Critical"

            || support__cw_ops_manage_case_merge[Priority] = "P2 - High"

            || support__cw_ops_manage_case_merge[Priority] = "P3 - Medium"

            || support__cw_ops_manage_case_merge[Priority] = "P4 - Low"

            || support__cw_ops_manage_case_merge[Priority] = "Non-Priority"

        )

    )

)

[lbendlin]

Read about the IN function in DAX.

[saud968]

Hehe yes i realized now when you mentioned in it... It will shorter and crisper Dax.. Thanks

[lbendlin]

Slicers and other filters cannot affect calculated columns.  Calculated columns are called calculated columns because they are calculated once, during semantic model refresh, and then never again.