4 Answers, 1 is accepted
Hi Michael,
I was able to recreate the abnormality in a local test and unfortunately we have to confirm that this is an issue in the present version of our controls. In my case I was able to corrupt the column resizing even without performing postback.
We will do everything possible to address it soon as this issue has been forwarded to our Development team.
In the meantime a temporary solution can be to use Visible="false" instead of Display="false" for a column property.
Here is a link to the issue I have reported so you can track its status.
Regards,
Deyan Enchev
Telerik
The observed behaviour is expected because since Q1 2013 cell data is not stored in the ViewState of the grid when the column is hidden(Visible=”false). You can read more about this breaking change here.
In your case best would be using DataKeyNames property in order to have values stored in the ViewState. This means that they are available at any moment.
“…If the Visible property of a column field is set to false, the column is not displayed in the GridTableView control and the data for the column does not make a round trip to the client. If you want the data for a column that is not visible to make a round trip, add the field name to the DataKeyNames property…”
Our online help explains how this can be done.
Deyan Enchev
Telerik