heya
I was alerted to this issue after having my production app up and running for months without issue. Essentially my client was editing a radgrid inside a radwindow via automatic updates and the standard out of the box edit mode. What would happen is that the client would have data as such:
edit fname0, lname0,0,0
edit fname1, lname1,0,0
edit fname2, lname2,0,0
the query in simple terms as "select fname,lname,col3,col4 from t1 order by col3"
when clicking on fname0, it would open to edit view, but the data would be random as fname1 or fname3 in the selected row.
This would also only happen on certain rowsets matching certain conditions. not that my query was set to order by col3, which in this case all happened to be zero. My suspicion is that it has to do with how the grid would resort itself on any item command. if the sort is to sort by a number for eg and the numbers it is presented are 0,0,0 instead of 0,1,50 the grid has no constraint. Once I added a second order by as 'order by col3,lname' my issues dissapeared.
don't have time to create a scenario for further testing as it was so peculiar, just thought I would post mt observations.
mac
I was alerted to this issue after having my production app up and running for months without issue. Essentially my client was editing a radgrid inside a radwindow via automatic updates and the standard out of the box edit mode. What would happen is that the client would have data as such:
edit fname0, lname0,0,0
edit fname1, lname1,0,0
edit fname2, lname2,0,0
the query in simple terms as "select fname,lname,col3,col4 from t1 order by col3"
when clicking on fname0, it would open to edit view, but the data would be random as fname1 or fname3 in the selected row.
This would also only happen on certain rowsets matching certain conditions. not that my query was set to order by col3, which in this case all happened to be zero. My suspicion is that it has to do with how the grid would resort itself on any item command. if the sort is to sort by a number for eg and the numbers it is presented are 0,0,0 instead of 0,1,50 the grid has no constraint. Once I added a second order by as 'order by col3,lname' my issues dissapeared.
don't have time to create a scenario for further testing as it was so peculiar, just thought I would post mt observations.
mac
1 Answer, 1 is accepted
0
Hello mac,
Tsvetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.
Since you do not have time to prepare a test project, for your convenience I have attached a sample one - could you, please, take a look at it and explain in detail, making illustrations on the sample, what the issue exactly is as I could not get it from the information you have supplied.
Thanks.
Regards,Tsvetoslav
the Telerik team
Instantly find answers to your questions on the new Telerik Support Portal.
Watch a video on how to optimize your support resource searches and check out more tips on the blogs.