Hello Yudi,

We are using WebGrid 7.0 in SharePoint. We are rendering the grid programatically. As we wanted to access the changes both on client side and server side, we have done the following settings::

interSoftWebUIGrid.LayoutSettings.StatusBarVisible = true;

interSoftWebUIGrid.LayoutSettings.AllowBatchUpdate = true;

interSoftWebUIGrid.LayoutSettings.BatchUpdateSettings.NotifyOnLostFocus = true;

interSoftWebUIGrid.LayoutSettings.BatchUpdateSettings.PromptUnsavedChanges = false;

With these settings, when we change anything in the grid and click on any other button on the page we WILL NOT get the prompt, which is what required, but we get a JavaScript error with the message : Error: 'null' is null or not an object.

Any help on this would be greatly appreciable.

Thanks,

G S

Hello Glenn,

                   Thanaks for your kind reply. As you said we can not remove that extra column, is there any way that we can reduce the width of that extra column? If we can, then please send me the sample code for doing the same.

Thanks,

G.S

Thanks for the solutions. By the way the zip file attachment is for some reason not downloadable, can you please check ?

I tried adding (rather associating) a hidden column with one of visible columns and i am now able to get its value from client side as described in your answer.

But the serious limitation with this approach is that i can have only one hidden data member per visible column. What if i am displaying only 5 columns but for other computation purpose need to access more than 5 other columns ( which is really the case in my scenario) ?

Is there a way i can access these hidden members from the columns for which i have set its 'visible' property to false ???

Thanks,

G.S

Yes i too notice that behaviour now. Supricingly i do have all the JavaScript files including WebGrid_core.js and WebGrid_UI.js in my  folder. Please find the attached screen shot to get an idea of what all files i am having in my folder.

This is now really driving us crazy, please help.

As you have mentioned we modified the code but we are still getting the same error :( 

Please find the attached code and the screen shot of the error for your refefence.