I have posted this under My IG with the case number: CAS-29509-U12QD8, however this is a pretty major bug, so I thought I'd post here to in order to hopefully get a fast answer.
When editing two cells on the same row and then clicking away from the second cell, only the second change will be persisted on PostBack.
Please perform the following on your Automatic CRUD for Custom Collections sample.
Only the second change on the row will be persisted. The first change will be lost.
However, if you press enter after the second edit both changes will go though. Or if you click Save Changes BEFORE leaving the editing mode on the second cell, the changes will also go though.
I'm afraid this didn't quite fix it for me.
If I edit two cells on the same row and then click to a different row, only the first change will be persisted. That is until I click to another row and then the second cell I edited will then update itself.
Also, with this enabled I'm getting errors with my editors, i.e. the first TextEditor Provider no longer allows any text entry and doesn't actually show the current cell text. Also any additional providers, i.e. the numeric provider for the ID column throw errors such as:
Microsoft JScript runtime error: Object doesn't support this property or method
Thanks for your response Vince.
As a note to anyone who's interested, handling the RowUpdating server-side event for your WebDataGrid seems to have corrected this issue for me.
You don't have to do anything inside the event handler, just handling the event alone seems to do it.
It's a workaround but it should help until Infragistics can fix the underlying problem.
Civel,
We're still in the process of investigating the support case that Will logged. We need to determine what's happening before we can provide any estimate as to when there may be a solution.
If you're encountering the same or a similar issue, you should submit a support request to provide information as to what you're seeing. Feel free to refer to this forum thread as part of the request.
Is there any more news on the timeline for fixing this bug? Will we have to wait for the next service release or will there be a fix coming sooner? Thanks.
Will,
We're still investigating this issue. We need to better understand what's happening and why before we may be able to provide a time estimate.
Thank you for your patience.