The PerformBacthUpdate method already have the option to update the WebGrid UI automatically by passing true in the second parameter of the method. However, since passing True causes JS error in the previous build; as a workaround, you will need to manually call refresh method for the WebGrid to update UI properly.

Since in the latest build this issue has been fix, passing true in the second parameter does not cause JS error, passing true in the PerformBacthUpdate method will update the WebGrid UI properly.

Awesome. That confirms that #2 has been fixed.

Can you also confirm that this is fixed too: 1) The 'rowErrors' start tag on line 2 does not match the end tag of 'BatchUpdateResult'. Line 2, position 167.

The fix for the issue I refer to in my previous post is the UpdateUI parameter set to True in PerformBatchUpdate method. With the fix in the latest build, we could pass True in the UpdateUI parameter in PerformBatchUpdate method so the UI will be updated properly.

Did you find another issue when using the latest build?

Please explain.  My last post refers to two seperate issues regarding the PerformBatchUpdate method. The first is that exception which appears to be fixed (I need to test but we are going through a deployment cycle)  The second is the UI not updating properly after the PerformBatchUpdate is called and the Intersoft workaround was to call the "WebGrid's Refresh" method which basically called a second postback.  This won't work for us so I am trying to see if this bug is fixed as well.

Thanks!

Do you mind providing a simple runable sample? Using an ASP button to invoke the PerformBatchUpdate in the batch update provided sample I could not replicate the issue. I could discuss the issue further with our developer if the issue is replicable in our environment.

It will take some time given the complexity of our software. Can you talk to the developer on what the exception might be? That might shed some light given it's a specific error message.

This is not a bug.

The Enabled property of WebGrid only works on full PostBack action. For example, set the value of Enabled property on the click event of ASP.NET button will get WebGrid in non-editable state (prevent users from entering input).

I enclosed one simple sample of WebGrid that will be disabled during the click event of ASP.NET button. WebFlyPostBackManager is utilized in order to turns the full PostBack of ASP.NET Button into FlyPostBack request (a.k.a callback) without javascript codes.

Please have the attached sample tested on your end and let us know whether it helps or not.

I disagree.  I don't understand how this could not be a bug. It's a client-side javascript property to enable/disable a grid but it doensn't fully enable/disable. What is the purpose of the property if I have to iterate through every single cell to set its SetForceNoEdit property which can be a huge performance hit or have to use a DIV element to prevent input? Also, I don't see why a PostBack would be necessary given it's client-side property. That makes no sense to me.

I was able to use this workaround but this should be addressed or the property removed because it doesn't work as expected. 

You could check the Client_ProgrammaticEdit.aspx provided WebGrid sample for implementation of WebGrid editing client side API. In short, you will need to be able to retrieve the new row object and invoke the update function. Here is the snippet assuming the new row is the selected row:

var grid = ISGetObject("WebGrid1");
grid.GetSelectedObject().ToRowObject().Update();

 

You don't understand my problem. The WebGrid will postback and update the data as focus is lost from the WebGrid. For instance, a user enters data in a new row and then clicks on a button. In my scenario, I have a WinForms application that uses a WebBrowser object to display a web page. This application has nodes that transports the user from web page to web page. In this case, the WebGrid doesn't detect focus lost so the update does not occur.

To fix, the WinForms calls a method on the web page that just calls window.focus() which triggers the update.