Intersoft Solutions - Community - WebGrid Enterprise

Posted: November 24, 2009 7:14 AM in response to Andi Santoso

Andi,

The reason I don't want to do it on the Client Side is that I have 8 grids to potentially save. That is 8 AJAX postbacks, and the "Save" button on my page must do a full page postback to save other controls also, so the whole process doesn't work so well.

Is there a plan to fix this bug anytime soon as it kinda seems pointless providing a Server Side method to perform the batch update if it isn't going to work.

A bettter workaround in this scenario would be to perform a Response.Redirect back to the same page as the last line of code executed in the postback.

Regards,

Adrian.

Andi SantosoSupport

Posted: November 25, 2009 4:57 AM in response to Adrian Cunningham

Hi Adrian,

Those are the PerformBatchUpdate’s behavior, as you might notice that, if you try to debug the code, the grdFactors_BatchUpdate is called after grdFactors.PerformBatchUpdate invoked. So, actually the batchupdate is run already and its behavior to leave the highlight on the WebGrid.

But here is the other way to remove the highlight on the WebGrid from the server side. But, no matter how, we still need to use a script to accept all changes in WebGrid and display it, that is why we need to call a java script in the server side.

Here are the sample code that I modify from your sample:

<<HTML>>

<script language="javascript" type="text/javascript">

// <!CDATA[

function update() {

 

            var grid = ISGetObject("grdFactors");

            

            window.setTimeout(function() {grid.AcceptAllChanges()},50);

                      

            return true;

        }

 

// ]]>

    </script>

<<C#>>

 

protected void btnSave_Click(object sender, EventArgs e)

{

             grdFactors.PerformBatchUpdate(true);

             this.ClientScript.RegisterStartupScript(this.GetType(), "a", "<script  	  	language=\"javascript\" type=\"text/javascript\">update();</script>");

 

 

}

Thank you,

Andi Santoso

Posted: November 25, 2009 7:46 AM in response to Andi Santoso

Andi,

I am aware that that PerformBatchUpdate method actually calls the grdFactors_BatchUpdate phyiscally saves the data to the database this is desired and documented functionality that I want, what it doesn't do is reflect this in the UI.

The idea (or so I thought) of batch update is to allow me to process multiple changes in one single batch. The documentation states that "In some cases you might prefer to have your own button process the pending changes, in addition to the user the interface provided by the WebGrid".

And this is one of those of those occasions. The PerformBatchUpdate method does physically update my datasource but leaves the datasource and the WebGrid UI in an inconsistent state, and this is a bug in my view.

Your previous post would actually result in processing the pending changes twice:

The PerformBatch Update method will process the changes correctly on the button slcik but fails to update the UI of the grid to reflect the processed changes.
The script sends a "Second" request to process the changes simply so the grid looks correct, I would have to do this for all 8 grids.

This completely negates the point of me processing pending changes with my own server side code, not to mention that fact that performance will be rubbish.

Regards,
Adrian.

Andi SantosoSupport

Posted: November 26, 2009 2:54 AM in response to Adrian Cunningham

Hi Adrian,

The WebGrid1_BatchUpdate behavior from server side is to Update the data in server but not for the layout. I am sorry for the inconvenince, but I have sent this issue to the development team and they will enhance this feature in next hotfix.

Thank you,
Andi Santoso

Jocelyn RendulicMember

Posted: February 22, 2010 4:53 PM in response to Andi Santoso

I am encountering the same problem. It still does not seem to work correctly. Any idea when this issue will be fixed?

Andi SantosoSupport

Posted: February 22, 2010 9:51 PM in response to Jocelyn Rendulic

Hi Jocelyn,

The issue is still under investigation. I will inform you as soon as I get news from developer team. Thank you and have a nice day.

Best Regards,

Andi Santoso

Posted: September 30, 2010 1:58 PM in response to Andi Santoso

Hey Andi,

Just wondering if this issue has been resolved yet as it is a bit of pain having to a Response.Redirect after every batch update.

Regards,

Adrian.

Andi SantosoSupport

Posted: September 30, 2010 10:02 PM in response to Adrian Cunningham

Hi Adrian Cunningham,

Yes, deeply apologize for the late respond. Could you kindly get our latest build of WebGrid? In our new hotfix, we introduced PerformBatchUpdate(throwOnError, updateUI).

In your case, you can simply try to use PerformBatchUpdate(true,true)

I hope it can help. Thank you and have a nice day!

Best Regards,

Andi Santoso

Shawn AugustMember

Posted: October 1, 2010 9:47 AM in response to Andi Santoso

Hi Adrian Cunningham,
Yes, deeply apologize for the late respond. Could you kindly get our latest build of WebGrid? In our new hotfix, we introduced PerformBatchUpdate(throwOnError, updateUI).
In your case, you can simply try to use PerformBatchUpdate(true,true)
I hope it can help. Thank you and have a nice day!
Best Regards,
Andi Santoso

I believe this method already exists in my release. Was it updated to fix this bug?

Andi SantosoSupport

Posted: October 3, 2010 10:19 PM in response to Shawn August

Dear Shawn,

Yes, I am pretty sure it will, with this PerfomBatchUpdatage(true,true), it will do the batchupdate and update the user interface as well.

I have tried to use this method under your scenario and it works nicely.

I hope it helps. Thank you and have a nice day

Best Regards,

Andi Santoso

Posted: October 4, 2010 3:15 PM in response to Andi Santoso

Andi,

Can you tell me the exact version of the WebGrid DLL I need that has this fix, as the version I have contains the method you refer to but I still get errors after doing a batch update via the "PerformBatchUpdate" method.

Regards,

Adrian.