Intersoft Community - WebGrid Enterprise - Expand All option on GroupHeaders doesn't work when PagingMode=VirtualLoad

Expand All option on GroupHeaders doesn't work when PagingMode=VirtualLoad

yudi — Tue, 16 Nov 2010 02:48:56 GMT

I need to discuss this feature request with WebGrid development team.
I’ll get back to you after I heard something from the team.

Thank you for your valuable feedback.

Expand All option on GroupHeaders doesn't work when PagingMode=VirtualLoad

mdearman@libera.com — Mon, 15 Nov 2010 09:29:53 GMT

Can this be controlled on a WebGrid property like "IgnoreVirtualLoadModeOnGroupExpandAll"? Even if the default is to only load 50. There are some scenarios where I need the user to be able to finish loading all records underneath all groups and automatically expand them.

Expand All option on GroupHeaders doesn't work when PagingMode=VirtualLoad

yudi — Mon, 15 Nov 2010 03:08:51 GMT

This behavior is not a bug and is by design.

When a virtual group is loaded, the “Expand All” command can expand the groups automatically. However, the groups that haven’t been fetched won’t be expanded. This is to avoid performance problem if there are a lot of groups that need to be fetched from server.

Please let us hear your response.

Expand All option on GroupHeaders doesn't work when PagingMode=VirtualLoad

yudi — Wed, 19 May 2010 23:47:55 GMT

When VirtualLoad™ and GroupedColumns features are enabled (assuming that VirtualPageSize property is set to 50), WebGrid will try to keep the number of loaded rows not more than 50 rows (to match with the VirtualPageSize property).

WebGrid will try to expand grouped columns one by one starts from first row and then count the number of loaded rows. After expanding the grouped columns, WebGrid will count how many loaded rows. If the amount of loaded rows is less than 50, then WebGrid will keep this grouped colum expanded; and then try to expand the next grouped column and do counting again. If the amount of loaded rows is exceeding than 50 rows, then WebGrid will collapse the last grouped column.

When group columns exist in top level Table, all parent group rows will be rendered to clients but only a number of defined rows are rendered counted from the first parent group row. When users click on “+” to expand group row, the control will transparently and virtually load the child rows of that group row.

I have forwarded the “Expand” and “Expand All” minor glitch to WebGrid development team. A work item, work item #718, has been submitted regarding this issue. I’ll keep you updated with any news I heard from the team regarding this.

Expand All option on GroupHeaders doesn't work when PagingMode=VirtualLoad

mdearman@libera.com — Wed, 19 May 2010 16:27:19 GMT

I have a grid groupped by a column (in my sample, one column), where the PagingMode=VirtualLoad and set to load 50 records and VirtualLoadMode=Default.

On the client-side, when I use the Expand All context menu option, it only expands the currently selected GroupHeader row, even though the next few groups only have a few records each (they didn't hit the 50 record limit during LoadGroup event).

This is confusing our users because there is no functional difference between "Expand" and "Expand All". Why doesn't Expand All work properly, even if it has to load all remaining records to the client-side.

Thanks,

Mike