Forum Discussion
Problem with visuals displaying the first N values and a dynamic "other" group
- Anonymous1 year ago
Hi, noviceBI
Thank you very much for your prompt response. I am glad that you are interested in my DAX, which reflects your humble and eager-to-learn attitude.
1.Firstly, regarding the meaning of SELECTEDVALUE. The SELECTEDVALUE function is used to return the value in the current context. If no value is selected, it returns a default value. You can understand it as returning the current row value in a measure. You can replace it with aggregation functions like MAX() or MIN(), and the result will only differ in the total section. This is related to the context dependency of measures.
For the difference between calculated columns and measures, you can refer to the following link:
Solved: What is the difference between a measure and calcu... - Microsoft Fabric Community
2.Secondly, adding the filter 'Incidents 2024'[Processus] IN VALUES('Processus avec autres'[Processus]) is mainly to aggregate the 'Processus avec autres'[Processus] field in our newly created calculated table. If you remove this filter condition, it will return the aggregated value of the 'Incidents 2024'[Processus] IN Processus1 field, which means it will return a fixed value for each row value of the 'Processus avec autres'[Processus] field. As shown in the figure below:
If you add this filter condition, it forms an AND condition. 'Incidents 2024'[Processus] IN Processus1 is to ensure that the returned value is in the TOPN and to aggregate each row value of the 'Processus avec autres'[Processus] field separately. For better understanding, you can also replace the filter 'Incidents 2024'[Processus] IN VALUES('Processus avec autres'[Processus]) with 'Incidents 2024'[Processus] = MAX('Processus avec autres'[Processus]), which is closely related to your first question. Our solution's overall idea is to return the aggregated result that meets the requirements based on the context of the 'Processus avec autres'[Processus] field. Theoretically, its return value should be the content of all 'Processus avec autres'[Processus], but the visualization automatically does not display empty values during aggregation.
3.Finally, regarding your third question, this is also related to the first question. As I mentioned earlier, the total section will be different. You can understand the total section as the output result of a card visual object without the context of the 'Processus avec autres'[Processus] field. Since the output result of SELECTEDVALUE is empty, and empty is not equal to the text "Autres", the output result is false.
The false result is CALCULATE( COUNT('Incidents 2024'[Incident]), 'Incidents 2024'[Processus] IN Processus1, 'Incidents 2024'[Processus] IN VALUES('Processus avec autres'[Processus]) ). You might wonder why it should not return empty here, but the return result includes the total value of all TOPN parts. This is why the VALUES() function is used. If you use 'Incidents 2024'[Processus] = MAX('Processus avec autres'[Processus]), the return result is empty, while VALUES() returns the entire column value in the total section.
For more details, please refer to:
VALUES function (DAX) - DAX | Microsoft Learn
If you need the total value to include all results, you can modify the measure as follows:
Measure = VAR Processus1 = SUMMARIZE( TOPN( [Parameter Value], SUMMARIZE(ALLSELECTED('Incidents 2024'), [Processus], "count", COUNT('Incidents 2024'[Incident])), [count], DESC ), [Processus] ) RETURN IF(ISINSCOPE('Processus avec autres'[Processus]), IF( MAX('Processus avec autres'[Processus]) = "Autres", CALCULATE( COUNT('Incidents 2024'[Incident]), NOT('Incidents 2024'[Processus] IN Processus1) ), CALCULATE( COUNT('Incidents 2024'[Incident]), 'Incidents 2024'[Processus] IN Processus1, 'Incidents 2024'[Processus] IN VALUES('Processus avec autres'[Processus]) ) ),COUNT('Incidents 2024'[Incident]))Here is the final result:
I hope my answer helps you understand. Of course, this is just my understanding of the practical application of the function.
For a more official explanation, you can refer to the following link:
DAX overview - DAX | Microsoft Learn
I believe you will become an even more outstanding user than us.Please find the attached pbix relevant to the case.
Best Regards,
Leroy Lu
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
o dynamically recalculate the ranking within the filtered context, follow these steps: 1. Modify the Ranking Measure to Work Dynamically Update your current ranking measure as follows: DAX Rang_Processus_Dynamic = VAR SelectedDateRange = ALLSELECTED('Incidents 2024'[Date]) -- This ensures the ranking respects the date filters RETURN RANKX( CALCULATETABLE( VALUES('Incidents 2024'[Processus]), SelectedDateRange -- Apply the selected date range ), [Total_Incidents], -- Rank based on the count of incidents ,DESC, DENSE ) This adjustment guarantees that the ranking updates dynamically when a date filter is applied. 2. Modify the Measure that Groups "Others" Next, revise your "Top 7 incidents avec autres" measure: DAX Top_7_Incidents_Avec_Autres = VAR CumulIncidents = SUMMARIZECOLUMNS( 'Incidents 2024'[Processus], "@Rang",[Rang_Processus_Dynamic], -- Utilize the new dynamic ranking "@Incidents",[Total_Incidents] ) VAR IncidentsCategorise = ADDCOLUMNS( CumulIncidents, "@NouveauProcessus", IF([@Rang] <= 7, [Processus], "Autres") -- Group lower-ranked incidents into "Others" ) VAR IncidentsFiltres = FILTER( IncidentsCategorise, [@NouveauProcessus] IN VALUES('Processus avec autres'[Processus]) ) RETURN SUMX(IncidentsFiltres, [@Incidents]).