Intersoft Community - WebGrid Enterprise - Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

Sir_Xblack — Wed, 02 Mar 2011 23:18:13 GMT

Hi,

I was create new issue at this link http://www.intersoftpt.com/Community/WebGrid/Cannot-use-VirtualGroupPaging-with-WebService-and-ADONET/

Thanks,

Huy

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

gordont — Wed, 02 Mar 2011 21:36:28 GMT

Hi Huy,

Please create a new thread for the new issue. Thanks.

Best Regards,

Gordon Tumewu

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

Sir_Xblack — Wed, 02 Mar 2011 00:13:54 GMT

Hi Intersoft,

I was tried to upgrade to WebGrid 7 but your example didn't work for me. When I try to expand a group, an exception appeared:

"Message":"A circular reference was detected while serializing an object of type \u0027System.Reflection.Module\u0027.","St...

I attached my sample to you.

I'm using ASP.NET 2.0 and VS2005 C#. I'm not using LINQ or ISNET LINQ DataSource, just only ADO.NET: DataSet and DataTable.

This is list dll I used in sample : Webgrid version is 7.0.7200.417 ; WebDesktop is 3.0.7200.322 ; WebCombo is 4.0.7200.232 ; System.Web.Extensions Version is 1.0.61025.0.

I'm not use ISNet.Data.Ling.dll

Another problem is the loading time for dataset with 500 rows. In my sample, I can see the progress icon loading take about 25s for just only 500 rows. Is this normal that loading webservice with 500 rows take about 25s? In my real application, I was faced to large data with more than 10.000 rows.

Please help me investigate why it couldn't run and is the webservice peformance too slow or not?

Thanks,

Huy

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

handy@intersoftpt.com — Tue, 22 Feb 2011 20:48:34 GMT

Hello Huy,

Unfortunately, this could not be done. WebGrid 6 has been discontinued. So, there would be no enhancement and hotfixes. We suggest you to consider in upgrading WebGrid 7.

Regards,
Handy

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

Sir_Xblack — Tue, 08 Feb 2011 22:12:43 GMT

Hi Intersoft,

I'm using WebGrid 6 and I have the same issue like Scott have with large data and grouping function.

Did you add virtual group paging to webgrid 6? I think webgrid 6 and 7 are not differences too much.

Can I use service pack of Webgrid 7 for version 6? I need this function in urgent case.

Thanks,

Huy

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

Glayaar — Tue, 23 Feb 2010 01:20:33 GMT

Attached is the modified WebService.cs that has been modifed to handle the grouping without linq provider. You will need to create WebGridGroupRow class to contain the grouping information. The function GetPagedBugs has another conditonal check for SelectOperation.SelectGroup that will handle the grouping functionality.

For each grouping, you will need to add another depth to the WebGridGroupRow construct. The required information for the construct id the group depth, group row position, next level of group row information, total grouped row count.

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

Glayaar — Wed, 17 Feb 2010 04:25:25 GMT

I am still discussing this issue with our developer, I will inform you if there is any update or progress regarding this issue.

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

sfrench@sierradata.com — Tue, 16 Feb 2010 14:59:46 GMT

Hi Glenn,

For this page we are using InitializeDataSource and there is a large amount of code specific to our own custom DAL and security settings in this sub. Converting this page to use LINQ and a WebService would require a huge development effort that we did not anticipate. Do I understand the situation correctly? Is the only way to get Group Row Paging to work using LINQ/WebService as the datasource?

Thanks,
Scott French

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

Glayaar — Mon, 15 Feb 2010 23:49:26 GMT

We have a sample of the scenario depicted in this article in our WebUI Studio 2009 R2 SP1 WebGrid sample on the page ClientBinding_VirtualGroupPaging_WebService.aspx. The sample is using the GetPagedBugs function to select the data and in the new sample, this function has been modified using technique in section WebGrid LINQ DataProvider.

You will need to modify the select method in your WebService as well using the LINQ DataProvider in order to automatically handle the select operations.

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

sfrench@sierradata.com — Fri, 12 Feb 2010 12:30:45 GMT

Hi Handy,

The blog linked above has 4 main sections. "Preload Group Totals", "Group Row Paging", "Virtual Load Support For Web & WCF Service", and "WebGrid LINQ Data Provider". We are only interested in the first two at the moment. "Preload Group Totals" looks to be working when following the directions. "Group Row Paging" is what we are talking about. All we did was add the GroupRowPageSize="200" tag into the ClientBindingSettings area. I don't see any other instructions to get this working.

Thanks,
Scott French

Lots of problems using WebGrid, Clientbinding, Batch Update and Grouping.

sfrench@sierradata.com — Mon, 02 Nov 2009 18:46:04 GMT

Hello,

We recently upgraded to WG7 and are in the process of upgrading one of our main grids to use Client Side Binding and Batch updates. One of my colleagues did the actual conversion so I don't know all of the specifics but I have been tasked with testing it. In many cases it functions correctly although there are a lot of issues to be dealt with. This post is largely focused on issues related to the grid being grouped. I have taken the WG7 sample for client side binding/batch updates and updated it to more closely match our setup. We are using "OnInitializeDatasource" to do our data-binding and have a lot of other settings that weren't in line with the original sample. I was able to reproduce a lot of the behavior by making this update. I could really use some guidance on dealing with these issues as there are a lot of them. These are only the ones I was able to reproduce in your sample today. There are many others related to deleting and saving where the page freezes or takes forever to complete an update. We ran into similar freezing issue when trying to group and ungroup columns. Those issues will have to be dealt with later. Please see the attached aspx/vb files (they can be placed in the WG7 sample folder) as well as the list below which provides the actual issues and steps to reproduce them.

FYI, we are using Web Grid dll version 7.0.7200.306. Nothing new is available when I go to the Update Manager so I am assuming this is the latest version.

Thanks in advance for any assistance in solving these problems!

1. Group Aggregate Row Counts are sometimes (0). The Row Counts as well as Group Sums change and/or disappear depending on the sort direction of the Group. Sort ASC and all Group Sums are missing and all Group Row Counts are (0). Sort DESC and the Sums will be displayed for some groups. These same Groups will have Row Counts while the others remain (0). It looks to me that if 100% of the group’s child records are not loaded in the initial 200 rows (our specified number of rows to load upon opening the grid) then the Group’s Row Count and Sums will not be calculated or displayed.
Steps to replicate

a. Open the sample file provided.

b. Group by ‘Component’ column.

c. The top few groups will have Row Counts but most will be (0).

2. Many times after saving or sorting when the grid is grouped most or all of the records will not be returned. Sometimes a partial list is returned, sometimes nothing. It seems to be related to the issue above. If 100% of the rows are loaded for the group that group will be returned. Otherwise after a save or sort the group will disappear.
Steps to replicate

a. Open the sample file provided.

b. Group by ‘Component’ column

c. Sort by any column.

d. Any Group with a Row Count of (0) will disappear. Refresh the grid and they will reappear.

3. Here is another issue that occurs when the grid is grouped. If we make a change to a record, then sort a column, the change will remain in the pending area at the bottom of the grid but the row itself will not show the change. The original value for that cell will return and the highlight color for the row will go away. After accepting all changes the new value shows up in the row.
Steps to replicate

a. Open the sample file provided.

b. Group by ‘Component’ column

c. Open a Group that has a row count above 0.

d. Make a change to the value in the “Changed In Last” column for at least one row.

e. Key off the row, the value changes, the row is highlighted and the “Pending Changes” area at the bottom the grid should reflect the changes made.

f. Now sort the grid by the “Changed In Last” column.

g. The changed row will no longer be highlighted and the edited cell will return to its original value, but the “Pending Changes” area will still reflect the changes that have been made.

h. Accept all changes and the original values will be replaced with the new ones.

4. I haven’t been able to replicate this issue in the sample yet but I wanted to pass it along in case it is a known issue and you have a solution. Opening a Group (clicking the plus sign) that has a lot of records (a few hundred) causes an error. “Stop running this script? A script on this page is causing Internet Explorer to run slowly. If it continues to run, your computer might become unresponsive.” This occurs even after we pulled all our custom code out of client side events OnSynchronizeCell and OnInitializeRow. Is there anything we can do to speed this up? It probably has to do with the large amount of data contained in each row being retrieved.

5. We are running into a lot of other issues with saving and deleting taking a really long time. Any feedback on converting over a large/complicated page (lots of server and client side custom code) from standard server side data-binding using “OnInitializeDataSource” to ClientSideBinding and SmartBatchUpdate would be much appreciated. We will likely follow up with more questions soon.