Glen,

Thanks for the reply, but if you look at my EDMCollection class I've actually implemented the ObjectRelations interface hence I thought I was already operating in "Inbound" mode.

However, I think I have got my app working with my own implementation while referencing your Tutorial Solution >> V4.0 >> Hierarchical_Binding.aspx tutorial.

Code below:

        protected void wgEDMPortfolios_InitializeDataSource(object sender, ISNet.WebUI.WebGrid.DataSourceEventArgs e)
        {
            List<BrokerEDMPortfolio> edmPorts2 = Controller.ServiceFacade.PortfolioNavigationService.GetBrokerEDMPortfolio(1752);

                        
            _edmColl = new EDMCollection(edmPorts2);
            e.DataSource = _edmColl;
        }

        protected void wgEDMPortfolios_PrepareDataBinding(object sender, ISNet.WebUI.WebGrid.DataSourceEventArgs e)
        {
            if (!IsPostBack)
            {
                wgEDMPortfolios.RetrieveHierarchicalStructure();
            }

        }

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:

1. 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.
2. 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.

James,

Thanks for this.  I've tried it out on the sample and there is a definite performance improvement.

I can't try it out on my actual application till next week as we've rolled back the controls for this release so I'll confirm if it solve my problem when I upgrade again next week.

Regards,

Adrian.

Handy,

I also think an issue I posted to the Devloper Network earlier in the year is possibly connected to this as the "IntegratedTo" property was causing me the same issue then.

WebToolBar Crashes IE [IS-F0A149C8-A17F-44F6-88F5-B90718928C4F]

Regards,

Adrian.

Handy,

From looking at your movie clip this is a definite increase in performance when the "IntegratedTo" property is set not set to a value "None".  Granted it may not be 1 minute but it certainly takes longer than with the "IntegratedTo" property set to None.

In out application using the WebMenuBar with this setting effectively kills out application and makes it unusable, but by simplying turning it off it is very fast.

Regards,

Adrian.