We recently upgraded our controls to the Q1 2013 SP2 assembly from 2011 0519. In making this change, we have noticed some significant changes to the way that some of the controls function.
• One of those issues is that the RadGrid control no longer accepts null or DBNull.Value in the DataFields. Changing the underlying data sets to return non-null values is not an immediate option for us since our solution is simply too large to identify all the places where that could be happening. We have been starting the process of re-working some of our pages to do this, but we have several hundred pages/user controls that need to be checked. In the meantime we need to find a work around to make the controls work similarly to the way they used to.
• The other issue is that the Visible=false property on a bound column is no longer maintaining ViewState properly. We know that we can change the Visible to Display and effectively get the old behavior, but there are many places where this was used.
We’ve been seeing other issues, but have not determined if they are due to a change in the Telerik controls or due to a recent upgrade to the latest jQuery library. Can you please at least help us to resolve these two issues?
Kindly let me know if you need any additional information.
Thanks.
3 Answers, 1 is accepted
The grid still supports null and DBNull, you can actually test this in our online demos for example this one:
http://demos.telerik.com/aspnet-ajax/grid/examples/automaticoperations/efdatabinding/defaultcs.aspx
Use the Display property instead of the Visible for hiding the columns if you need they to be persisted in the ViewState. Check this forum thread for more information:
http://www.telerik.com/community/forums/aspnet-ajax/grid/breaking-change-hidden-column-cell-text-is-not-persisted-in-viewstate.aspx
Regards,
Vasil
the Telerik team
Rank 1
It turned out that the issue is with the GridGroupByField of the RadGrid,when we are passing NULL values to it,we are getting the following exception as mentioned below:
Is that the NULL values are not supported in Q1 2013 SP2 Release?
We had this working with 2011 0519 Release.
Thanking you.
1) Exception Information
*********************************************
Exception Type: System.NullReferenceException
Message: Object reference not set to an instance of an object.
Data: System.Collections.ListDictionaryInternal
TargetSite: Boolean
You can turn this feature off by setting MasterTableView.EnableLinqGrouping=false. And see if there is any difference.
Regards,
Vasil
the Telerik team