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
gvg
Post Prodigy
Post Prodigy

Testing how Filter works

Hi experts,

 

I came accross this strange FILTER behaviour. Maybe it is because of my lack of understanding of DAX. I have this measure defined to test CALCULATE-FILTER behaviour:

 

 

Test filter = CALCULATE(SUM(Table1[Sales]), FILTER(Table1, Table1[Sales] < 70))

However, I must say, I am rather surprised what I get:

 

 

Untitled.png

Can you help, please, understand, why am I getting this result instead of obvious 90? 

 

3 ACCEPTED SOLUTIONS
MFelix
Super User
Super User

Hi @gvg,

 

Looking at your model you have several lines and your table shows the sum of the several regions if in your table you filter out the  values that era lower than 70 you will get the 180:

 

70.png

 

When you use measures this are based on context so when you add filter to your measure you are getting in the card visual all the lines that are below 70 (green part) that sums up 180.

auvergauverne, 

In you case you want to calculate the regions that have a total sales that are below 70 in this case  only Auverne, Picardy and Sardinia you need to redo your measure to a different context:

 

Test filter =
CALCULATE (
    SUM ( Table1[Sales] );
    FILTER (
        SUMMARIZE (
            ALL ( Table1[Country]; Table1[Region]; Table1[Sales] );
            Table1[Country];
            Table1[Region];
            "sales"; SUM ( Table1[Sales] )
        );
        [sales] < 70
    )
)

As you can see below the total is 90.

.filter.png

Explanation of meausre: In the filter I'm making a calculated table that reflects the summary table that you have  so in this case I'm using the Country and Region and making the sum of the sales for those columns (grouping sales) so the filter is made not over the full dataset but over the dataset with the grouping by region so when you filter only the ones that are lower than 70 you will get the correct value.

 

Attach the PBIX file for you to review it.

 

Regards,

MFelix

 


Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português



View solution in original post

Hi @gvg,

 

As I said measures are calculated based on context so when you have you table visual the country and region gives you context over the calculated measure, however when you put the same measure on a card the context of that measure is different and is provided by the filter /slicer that you aplly to that specific visual.

 

As you can see below if you add your measure to the table you have you will only get numbers on the country/regions that  correspond to the filter you  place in because the table is giving the context (grouping) that the calculation needs to provide the correct result, so depending on the type of visual the same measure can give you different results.

 

Also as you can see below the measure that I wrote if you add it to the table you will always get 90 for all rows, since the use of ALL in the filter overlapping the table context that we define in each row.

 

foilll.png

 

Regards,

MFelix

 

 


Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português



View solution in original post

Hi @gvg,

 

No because you are summing the total sales the SalesX is a column to filter out the information you need it's not included in the calculation as a variable.

 

To make it that way you should have the temporary table calculated as a variable and then use it on the SUM.

 

Regards,

MFelix


Regards

Miguel Félix


Did I answer your question? Mark my post as a solution!

Proud to be a Super User!

Check out my blog: Power BI em Português



View solution in original post

14 REPLIES 14

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.