Hi,
I've got a problem with a project I've updated from v7.2 to v8.1.
The page consists of a paged Grid with rows each with a single checkbox for each item in the grid. The problem occurs with paging and is as follows.
Modify a few of the checkbox values by clicking on the rows.
Change the page index.
The grid crashes with the following error:
System.NullReferenceException: Object reference not set to an instance of an object. at Infragistics.WebUI.UltraWebGrid.UltraWebGrid.UpdateDBRow(UltraGridRow row, UltraGridRow oldRow) at Infragistics.WebUI.UltraWebGrid.UltraWebGrid.ProcessChanges(StateChanges stateChanges, Boolean fireEvents) at Infragistics.WebUI.UltraWebGrid.UltraWebGrid.LoadPostData(String postDataKey, NameValueCollection values) at System.Web.UI.Page.ProcessPostData(NameValueCollection postData, Boolean fBeforeLoad) at System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint)
This is because the code in the page index changed is basically copied from the online help i.e. it does the following:
grid.RaisePostDataChanged() - Causes a call to UpdateCellBatch()
grid.PageIndex = e.NewPageIndex()
Grid.DataBind()
When calling the databind the above error is generated.
so I could take out the databind() and this fixes the above error. The question is where do I move this to. Is there any help for how to do this. I'm having a little trouble deciphering the code.
Thanks,
Andy
My issue was related to the data binding of the grid. After the check box was changed then processing occurred server side. The grid was then re bound to the data source. That was the issue. The solution was to move the call to the data binding out of the existing routine and put it in the "UpdateGrid" event of the grid itself.
Hope it helps.
I'm having the same issue on a page that was previously working in 2008.2 since upgrading to 2008.3:
[NullReferenceException: Object reference not set to an instance of an object.] Infragistics.WebUI.UltraWebGrid.UltraWebGrid.UpdateDBRow(UltraGridRow row, UltraGridRow oldRow) +179 Infragistics.WebUI.UltraWebGrid.UltraWebGrid.ProcessChanges(StateChanges stateChanges, Boolean fireEvents) +1520 Infragistics.WebUI.UltraWebGrid.UltraWebGrid.RaisePostDataChangedEvent() +126 System.Web.UI.Page.RaiseChangedEvents() +165 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +3518
Did you determine a solution for this?
Hello,
This could be an issue in the new version of the grid, or something in the setup/environment. Unfortunately it is very hard to tell based on the description and I am not sure we can figure this out in peer-to-peer forums. I believe that best case to proceed in cases like that is to contact Developer Support directly, if possible, with a small subset of your project reproducing the issue and some info on environment. Developer Support can be reached at:
http://ko.infragistics.com/support/
Thank you.
I am running into a similar problem with an app that was upgraded from .Net 2003 to vs 2008 clr 2. I have a simpe grid - no paging - with check boxes in one column the grid is on a warp panel and does a post back when the check is changed. It all worked fine in earlier versions but now I get a dump with the following. I have rebuilt the grid with no better results. Did you ever find a resolution to your issue?
An unhandled exception was generated during the execution of the current web request. Information regarding the origin and location of the exception can be identified using the exception stack trace below.
Stack Trace:
[NullReferenceException: Object reference not set to an instance of an object.] Infragistics.WebUI.UltraWebGrid.UltraWebGrid.UpdateDBRow(UltraGridRow row, UltraGridRow oldRow) +115 Infragistics.WebUI.UltraWebGrid.UltraWebGrid.ProcessChanges(StateChanges stateChanges, Boolean fireEvents) +1186 Infragistics.WebUI.UltraWebGrid.UltraWebGrid.RaisePostDataChangedEvent() +147 System.Web.UI.Page.RaiseChangedEvents() +117 System.Web.UI.Page.ProcessRequestMain(Boolean includeStagesBeforeAsyncPoint, Boolean includeStagesAfterAsyncPoint) +1646
I don't know what's causing this. It might be a bug, or it might be a problem in the application.
I suggest that you submit a support request so that a Developer Support Engineer can look into this in more detail. We'll likely need you to provide a sample project that we can run and debug that demonstrates this behavior.