In previous versions of WebDataGrid, if AutoCRUD=false was set, then all the editing could be handled manually. With this current version, the WebDataGrid attempts to lookup all the changed rows by key during a postback even when AutoCRUD=false. If the Grid isn't reloaded at the beginning of the postback or if any of the rows no longer exist an exception occurs: Requested record cannot be found by key. (Infragistics.Web.UI.GridControls.MissingRecordException).
In my web application, the edits are performed first to multiple rows and then the grid is reloaded at the end. Loading it at the beginning too would hurt performance, but the more important problem is that if any of the rows are removed by one user while another user is editing the grid (this is very likely) an exception will occur if the WebDataGrid looks for the missing rows instead of allowing the custom code to handle the updating.
Is there some property other than AutoCRUD that needs to be set for this version to disable the automatic row updating in the WebDataGrid?
@HunterDevelopment
What's your DataSource? When and how are you binding it to WebDataGrid?
Did you set EnableDataViewState = true?
I'm having the same trouble as well. Honestly, I can't figure out how to make the grid work properly with a collection. If I do row updating via AutoCRUD the server-side event doesn't allow me to change screen data. If I turn off AutoCRUD and handle the update via an ASP update button then I get the MissingRecordException. What am I missing?
Ok, so I have managed to find a work around for this, but the update didn't appear to solve the problem.
In the RowSelectionChanged event of Grid1, if you add the lines
(Reset all parameters fo the data source here)
Grid2.ClearDataSource()
Grid2.DataSourceID = "sqlDataSource"
Grid2.DataBind()
The most recent grid is returned to the client and everything works as expected.
If you don't clear the data source the original data source before you reset any parameters is returned.
I set <ig:EditingCore AutoCRUD="False"> in <Behavious> and <ig:WebDataGrid EnableDataViewState="True" EnableViewState="True">. It works fine. I think maybe Infragistics has already fixed the bug because I downloaded the controls on 1/27/2011.