Get certified for free when you join Fabric Data Days 2026 and dive into Fabric, Power BI, SQL, AI, and other essential data skills.
Join nowJuly 28 - August 9 | Final Round of the Power BI Dataviz World Championships. This is your chance. Learn more
The format of the column is Text+number. Although it's in the correct order in Power Query Editor, after applying the transformations (only deleted 2 columns and changed the data types), it completely jumbles up in the Data Tab in Power BI interface regardless of trying to sort it by the column (and this particular column). Please refer to the following tables to understand the problem:
Power Query Editor:
| Year |
| FY20 |
| FY20 |
| FY20 |
| FY21 |
| FY21 |
| FY21 |
Data Tab in Power BI Interface:
| Year |
| FY20 |
| FY21 |
| FY21 |
| FY20 |
| FY20 |
| FY21 |
I am unable to understand the underlying issue and its corresponsing solution. Any help would be deeply appreciated!
Thanks,
Novice_
Solved! Go to Solution.
The order of the rows in the table won't impact any of your visuals/analyses. If needed, you can add sort by columns to get a category column's values to display in something other than alphabetical order. In your case, FY20 will come before FY21 in a visual.
Pat
To learn more about Power BI, follow me on Twitter or subscribe on YouTube.
The order of the rows in the table won't impact any of your visuals/analyses. If needed, you can add sort by columns to get a category column's values to display in something other than alphabetical order. In your case, FY20 will come before FY21 in a visual.
Pat
To learn more about Power BI, follow me on Twitter or subscribe on YouTube.
If you love stickers, then you will definitely want to check out our community sticker challenge, Barcelona edition!
Check out the July 2026 Power BI update to learn about new features.
| User | Count |
|---|---|
| 4 | |
| 2 | |
| 2 | |
| 2 | |
| 1 |