Forum Discussion
Plan module (used to be powertable), single select columns becomes blank when sorted.
We have used powertable before, and have migrated into the plan module to have our master data, including our Employee table
When sorting by ReportingTo the EmployeeName column becomes blank.
I have added the configuration of the EmployeeName but its similar to Initials that is not affected
Does anyone have any idea of what is going on?
Had it affected all single select column the error had been consistant, but EmployeeName and Initials are both using the same jira.user table in its look up.
Hi ErikWarming,
Thank you for the detailed breakdown this is exactly the kind of systematic test that helps pinpoint the root cause.
Looking at the pattern you've identified, there's a clear split:
- Blanks on sort: EmployeeName, Initials, EmploymentType, EmploymentTitle, ReportingTo, the blurred column → all lookup/display-field columns
- Normal on sort: ID, FullTimeEquivalent, ValidFrom, ValidTo → all direct value columns
This strongly suggests a rendering bug in the Plan preview: when the grid re-orders rows after a sort, it's not re-fetching the display values for lookup columns only the underlying stored keys are re-rendered, but the label resolution fails.
Since you're on Plan (preview) as of 21/04/2026 on F8, this is most likely a known or unreported preview bug rather than a misconfiguration on your side.
Recommended next step: Report it directly via the Fabric feedback portal so the product team can track it:
👉 https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideasInclude your SKU (F8), region (North Europa), and the exact sort steps to reproduce. The more precise the repro steps, the faster it gets triaged.
In the meantime, as a workaround, try resetting the sort (click away from the sort column) this should restore the display values without a full page refresh.
Hope this gets resolved quickly in an upcoming preview update! Don't hesitate to give the kudo 😉
5 Replies
- Tamanchu
Super User
Hi ErikWarming,
Thank you for the detailed breakdown this is exactly the kind of systematic test that helps pinpoint the root cause.
Looking at the pattern you've identified, there's a clear split:
- Blanks on sort: EmployeeName, Initials, EmploymentType, EmploymentTitle, ReportingTo, the blurred column → all lookup/display-field columns
- Normal on sort: ID, FullTimeEquivalent, ValidFrom, ValidTo → all direct value columns
This strongly suggests a rendering bug in the Plan preview: when the grid re-orders rows after a sort, it's not re-fetching the display values for lookup columns only the underlying stored keys are re-rendered, but the label resolution fails.
Since you're on Plan (preview) as of 21/04/2026 on F8, this is most likely a known or unreported preview bug rather than a misconfiguration on your side.
Recommended next step: Report it directly via the Fabric feedback portal so the product team can track it:
👉 https://community.fabric.microsoft.com/t5/Fabric-Ideas/idb-p/fbc_ideasInclude your SKU (F8), region (North Europa), and the exact sort steps to reproduce. The more precise the repro steps, the faster it gets triaged.
In the meantime, as a workaround, try resetting the sort (click away from the sort column) this should restore the display values without a full page refresh.
Hope this gets resolved quickly in an upcoming preview update! Don't hesitate to give the kudo 😉
Thank you Tamanchu
I'll make a report at the Fabric feedback portal. 🙂
Your kudo is well earned
I came up with an ugly workaround, with a reference column based on the initials, that then returns the employee name. Its not pretty but it solves the inidiate problem
- Tamanchu
Hi ErikWarming,
Interesting issue inconsistent behavior between two columns sharing the same lookup (jira.user) points to a column-level configuration difference rather than a data problem. Here are a few things to check:
1. Compare the column definitions closely
Even if both use jira.user, check if EmployeeName and Initials have different display field or value field mappings. A mismatch between what is stored vs. what is displayed can cause blanks when sort order changes row rendering.2. Check the sort interaction with the lookup binding
When you sort by ReportingTo, does the EmployeeName go blank immediately or only after scrolling? If it's scroll-dependent, this is likely a lazy loading / virtual rendering issue where the lookup re-fetch fails for some rows.3. Test without sorting
Confirm that EmployeeName displays correctly without any sort applied if yes, the issue is triggered specifically by the sort reordering the dataset.4. Share screenshots of the column configuration
A screenshot of the EmployeeName vs Initials column settings in the Plan module would help pinpoint the difference.Could you also confirm which version of the Plan module you're on?
Thank you for some really good input Tamanchu
- the configuration of Initials and EmployeeName do not differ significantly.
- I start by clear existing sorting (on the ID column) then I sort by ReportingTo, then EmployeeName turns blank imidiatly. When I scroll, and when I set the screen to be paged. The EmployeeName stays blank.
- If I sort only by
- ID: everything looks normal
- EmployeeName: everything looks normal
- Initials: The initials column becomes blank
- EmploymentType: The EmploymentType column becomes blank
- EmploymentTitle: The EmploymentTitle column becomes blank
- FullTimeEquivalant: everything looks normal
- ReportingTo: EmployeeName column become blank
- Teamlead is a check box and cant be sorted
- The bluered column: The blured column becomes blank
- ValidFrom: everything looks normal
- ValidTo: everything looks normal
- I agree with your conclution that the disaperence of the lookup value happens when data is sorted
- Its Plan (preview) as of 21/4-2026 but other than that I cant find a version. Other than we are on a SKU:F8 fabric in North Europa
- the configuration of Initials and EmployeeName do not differ significantly.
UPDATE: I can see that the problem has been solved from Fabrics side.
