cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Resolver I
Resolver I

DAX ALL FUNCTION

Hi Everyone,

 

I have a measure that returns the total number of opportunities regardless of their stages within the selected period.

 

Number of Opportunities = CALCULATE(DISTINCTCOUNT('Opportunities'[Id]), ALL('Opportunities'[Stage]), DATESBETWEEN('Opportunities'[CreatedDate], MIN('Calendar'[Date]), MAX('Calendar'[Date])))

I noticed one thing very strange. I have a table with all stages and the measure above as the value. The measure value should stay the name if I change the Stage filter as I have used a ALL function. However, when I choose Closed - Deal Abandoned, the value changed to 310.

Example.jpg

WExample 2.jpghat might be the reason for this? Thanks.

 

 

 

 

 

 

1 ACCEPTED SOLUTION

Accepted Solutions
Highlighted
Super User III
Super User III

Re: DAX ALL FUNCTION

Hey,

 

this behavior is due to data distribution in your underlying table "Opportunities" and a concept called "Auto-Exist", this article explains this concept in greater detail: https://www.sqlbi.com/articles/understanding-dax-auto-exist/

 

If you need more assistance to spot the cause for the unexpected result it will become necessary that you share your pbix file with the data.

 

Nevertheless, my recommendation,

  • create a separate table that contains all the distinct values of the different stages
  • link this new table to your existing table "opportunities", the new table is the one side of the new relationship
  • use the new table in your measure
  • use the new table to filter your data

Hopefully, this provides some new insights.

 

Regards,

Tom



Did I answer your question? Mark my post as a solution, this will help others!

Proud to be a Super User!
I accept Kudos 😉
Hamburg, Germany

View solution in original post

1 REPLY 1
Highlighted
Super User III
Super User III

Re: DAX ALL FUNCTION

Hey,

 

this behavior is due to data distribution in your underlying table "Opportunities" and a concept called "Auto-Exist", this article explains this concept in greater detail: https://www.sqlbi.com/articles/understanding-dax-auto-exist/

 

If you need more assistance to spot the cause for the unexpected result it will become necessary that you share your pbix file with the data.

 

Nevertheless, my recommendation,

  • create a separate table that contains all the distinct values of the different stages
  • link this new table to your existing table "opportunities", the new table is the one side of the new relationship
  • use the new table in your measure
  • use the new table to filter your data

Hopefully, this provides some new insights.

 

Regards,

Tom



Did I answer your question? Mark my post as a solution, this will help others!

Proud to be a Super User!
I accept Kudos 😉
Hamburg, Germany

View solution in original post

Helpful resources

Announcements
August 2020 Community Challenge: Can You Solve These?

August 2020 Community Challenge: Can You Solve These?

We're excited to announce our first cross-community 'Can You Solve These?' challenge!

July 2020 Community Highlights

July 2020 Community Highlights

Learn about the exciting things that happened in July.

Featured Data Story of The Month

Featured Data Story of The Month

All Data Stories Gallery contributions are reviewed for each month. We select a contribution and feature the community member the following month.

Power BI Dev Camp - Developing with .NET Core

Power BI Dev Camp - Developing with .NET Core

Learn how to develop custom web applications for Power BI using .NET Core 3.1 and .NET 5.

Power BI Desktop August 2020 Update

Power BI Desktop August 2020 Update

We have great updates this month! Click the link for the video with more info.

Top Solution Authors
Top Kudoed Authors