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.
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.
Covering the world! 9:00-10:30 AM Sydney, 4:00-5:30 PM CET (Paris/Berlin), 7:00-8:30 PM Mexico City
Check out the April 2024 Power BI update to learn about new features.
User | Count |
---|---|
113 | |
104 | |
77 | |
67 | |
63 |
User | Count |
---|---|
144 | |
107 | |
105 | |
82 | |
69 |