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.
I'm confused as to why the "Top N" for the whole number field of yearnbr wouldn't pick the same order as sort order? Any suggestions?
I worked around it by creating a rankx column for year, and then use that as the "by value". But I don't think any work around should be nessary.
Solved! Go to Solution.
Thanks for posting. Looking at your pbix file I noticed that it was sum of year. The issue is I'm using a date table that has far more than just year. So my sum of yearnbr is causing the issue. Being a leap year the total for 2016 is higher than 2017.
Once I changed from sum to max value the sort order was correct.
Hi @Doby42 ,
Based on my test, the TOPN Filter works fine on my side, could you please reproduce this issue in my shared sample pbix file?
BTW, pbix as attached.
Best regards,
Community Support Team _ Dong Li
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Thanks for posting. Looking at your pbix file I noticed that it was sum of year. The issue is I'm using a date table that has far more than just year. So my sum of yearnbr is causing the issue. Being a leap year the total for 2016 is higher than 2017.
Once I changed from sum to max value the sort order was correct.
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 |
---|---|
109 | |
98 | |
77 | |
66 | |
54 |
User | Count |
---|---|
144 | |
104 | |
100 | |
86 | |
64 |