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!Calling all Data Engineers! Fabric Data Engineer (Exam DP-700) live sessions are back! Starting October 16th. Sign up.
Hello, all! I encountered unexpected behavior when assigning a row label and key column to a table. When doing so under certain conditions, all "sort by column" settings on that table appear to no longer be reflected in the report view. Here is a minimal reproducible example.
I have a single dimension table (note that the order column differs from the natural order of the description):
Key | Description | Order |
1 | Title A | 1 |
2 | Title B | 3 |
3 | Title C | 2 |
In the data view, I set the "Description" column to sort by the "Order" column.
In the model view, I set "Description" as the row label, then I set "Key" as the key column of this table (no issues seem to occur if the row label is set after the key column).
In the report view, I created a simple stacked column chart, with the "Description" column for the X-axis and "Count of Key" for the Y-axis.
Based on the table that I provided and the "Sort by column" settings, I expect the order of the columns to be "Title A", "Title C", "Title B", but the visual instead shows "Title A", "Title B", "Title C". The description column appears to be ignoring my specification to sort by the "Order" column, and is instead just sorting by itself. I cannot use "Sort axis" on the visual to sort correctly.
If it is helpful to diagnose the issue, I have discovered a few ways to "resolve" the issue.
For now, I can simply not use key columns, but I would like to be able to use Power BI as intended.
Here is a link to my Power BI file: https://drive.google.com/file/d/11hJHStJmGy08Hdq1heE1TtOYlg7UyNoh/view?usp=sharing
Thank you for your attention.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.