Hi,
When using certain column names in a Telerik WPF grid, the corresponding values are not being displayed correctly. The issue occurs when attempting to show data in the grid with the following column names :
Data = new ObservableCollection<CustomDynamicObject>()
{
new CustomDynamicObject(new Dictionary<string, object>
{
{"Check bug", "OK"}, // Values displayed correctly
{"Check. bug.", "OK"}, // Values not displayed correctly
{"Check. bug", "OK"}, // Values not displayed correctly
{"Check.", "OK"}, // Values not displayed correctly
{"Check ", "OK"}, // Values not displayed correctly
{"Check bug.", "OK"}, // Values displayed correctly
{"Check bug ", "OK"}, // Values displayed correctly
})
};
<telerik:RadGridView ItemsSource="{Binding Data}"/>
Data = new ObservableCollection<CustomDynamicObject>()
{
new CustomDynamicObject(new Dictionary<string, object>
{
{"Check bug", "OK"}, // Values displayed correctly
{"Check. bug.", "OK"}, // Values not displayed correctly
{"Check. bug", "OK"}, // Values not displayed correctly
{"Check.", "OK"}, // Values not displayed correctly
{"Check ", "OK"}, // Values not displayed correctly
{"Check bug.", "OK"}, // Values displayed correctly
{"Check bug ", "OK"}, // Values displayed correctly
})
};
(CustomDynamicObject is a custom class that implements DynamicObject with Dictionary<string, object>())
Expected Behavior :
Observed Behavior :
After binding the data object to the grid, some values are not visible for specific column names. This issue appears to be related to column names that contain special characters such as periods (".") and spaces. Consequently, users cannot view the complete dataset, leading to data misinterpretation.
Additional Notes:
This issue severely impacts the usability of our application, as users rely on the accurate display of data in the grid. We use dynamic objects because the user generates the SQL requests. Is it a bug? There is any workaround or alternative approach using dynamic objects
that would allow us to display the data correctly in the grid, we would
be grateful for your guidance on implementing it ?
Attached you'll find a simplified example of how to reproduce the bug and a screenshot.
If you require any additional information or assistance in reproducing the bug, please do not hesitate to reach out. We are eager to see this issue addressed as soon as possible.
Best regards,