Join us at FabCon Atlanta from March 16 - 20, 2026, for the ultimate Fabric, Power BI, AI and SQL community-led event. Save $200 with code FABCOMM.
Register now!To celebrate FabCon Vienna, we are offering 50% off select exams. Ends October 3rd. Request your discount now.
From a column with the year, which today goes from 1980 to 2009 -although in the future it will start in 1960-, I have created two others with the decade, one of whole type, decada, (1980, 1990, 2000) and another of text type, decada_texto (80s, 90s, 00s). For the purposes of the problem that I am going to comment on below, it does not matter if I create them from Power Query or as calculated columns.
PowerBI orders decada_texto such that "00s -> 80s -> 90s", so I have ordered it according to decade, which being an integer does not suffer from this type of problems, so that the order is "80s -> 90s -> 00s".
Well, the problem is that doing this raises a problem with ALL(); if we count the number of different decades that exist and tell you not to take into account the filter context for the decada_texto itself:
decadas = CALCULATE(DISTINCTCOUNT(listas_spotify[decada_texto]), ALL(listas_spotify[decada_texto]))
Here's the result:
ALL() has no effect.
If you "disengage" decada_texto of a decade (note that the order is again "00s -> 80s -> 90s"):
ALL() is back to normal operation.
What way is there to solve this while maintaining the order I want?
Greetings and thanks in advance.
Solved! Go to Solution.
I think if you add a second ALL referring to your sort column it will fix it. The sort column is added into the filter context at the same time as the main column.
I think if you add a second ALL referring to your sort column it will fix it. The sort column is added into the filter context at the same time as the main column.
User | Count |
---|---|
98 | |
76 | |
76 | |
49 | |
27 |