This time we’re going bigger than ever. Fabric, Power BI, SQL, AI and more. We're covering it all. You won't want to miss it.
Learn moreDid you hear? There's a new SQL AI Developer certification (DP-800). Start preparing now and be one of the first to get certified. Register now
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.
Check out the April 2026 Power BI update to learn about new features.
Sign up to receive a private message when registration opens and key events begin.
If you have recently started exploring Fabric, we'd love to hear how it's going. Your feedback can help with product improvements.
| User | Count |
|---|---|
| 7 | |
| 5 | |
| 4 | |
| 4 | |
| 3 |