The reported behavior is due to a LINQ exception caused by a type mismatch. Generally, when a DynamicObject
is used, the data engine resolves the data type of a given property based on the data type of the relevant property of the first item. So, in this particular scenario, it tries to apply an object of type DBNull
to a property of type String
. Thus, an ArgumentException
is raised and internally caught.
On the other hand, applying a null value to it a string property is a valid operation, thus the control is working as expected. I am afraid that there is not much we can do for this scenario, so I suggest you sticking to the approach you've already adopted.
All the best,
Telerik by Progress
Do you need help with upgrading your AJAX, WPF or WinForms project? Check the Telerik API Analyzer
and share your thoughts.