Component
Full Dashboard
Performance Monitor Version
2.4.1
SQL Server Version
SQL Server 2019
Windows Version
Windows Server 2022
Describe the Bug
When sorting columns that contain numeric values (e.g. size, duration, counts), the data is treated as text rather than numeric. This results in incorrect ordering, as values are sorted lexicographically instead of numerically.
This behaviour is observed across multiple grids where numeric values are displayed.
The FinOps model classes store numeric values like "Size GB" and "Rows" as string properties (for display formatting with commas/decimals), but the XAML DataGrid columns don't specify SortMemberPath to separate numeric sort properties. WPF then sorts these lexicographically (like text) instead of numerically.
Steps to Reproduce
- Open the Dashboard (Full or Lite)
- Navigate to the Finops grid containing numeric values (e.g Index Analysus)
- Click the column header to sort ascending or descending (Size GB/Rows etc)
- Observe the ordering
Expected Behavior
Size GB:
870.4
99.598
78.22
9.8
8.2
Actual Behavior
Size GB:
99.598
9.8
870.4
8.2
78.22
Error Messages / Log Output
Screenshots
Additional Context
Likely due to values being treated/rendered as strings rather than numeric types
Issue is UI-level sorting rather than data collection
Component
Full Dashboard
Performance Monitor Version
2.4.1
SQL Server Version
SQL Server 2019
Windows Version
Windows Server 2022
Describe the Bug
When sorting columns that contain numeric values (e.g. size, duration, counts), the data is treated as text rather than numeric. This results in incorrect ordering, as values are sorted lexicographically instead of numerically.
This behaviour is observed across multiple grids where numeric values are displayed.
The FinOps model classes store numeric values like "Size GB" and "Rows" as string properties (for display formatting with commas/decimals), but the XAML DataGrid columns don't specify SortMemberPath to separate numeric sort properties. WPF then sorts these lexicographically (like text) instead of numerically.
Steps to Reproduce
Expected Behavior
Size GB:
870.4
99.598
78.22
9.8
8.2
Actual Behavior
Size GB:
99.598
9.8
870.4
8.2
78.22
Error Messages / Log Output
Screenshots
Additional Context
Likely due to values being treated/rendered as strings rather than numeric types
Issue is UI-level sorting rather than data collection