Hello Frank,

Please kindly open our WebGrid Tutorial project>>V3.5>SelfHierarchyLoadOnDemand.aspx. You can see in behind code, what events are used. Basically in OnLoadDemand scenario, it should be clear. The row would be loaded based on demand by user. It would load the childs of selfReference row after it expands the row.

Regards,
Handy

The sample works fine until I introduce Paging. I want to use it for a self-reference grid with about 3,000 parent rows. Each parent has between 0 and 100 children (and sub-children).

In LayoutSettings, after GridLineColor="236, 233, 216", enter the following:

PagingMode="VirtualLoad"
VirtualPageSize="4"
VirtualLoadMode="LargeData"

The attached images show the results of these changes.

The first image (SelfReference_NoCodeChange) shows before any code is changed.

The second image (SelfReference_CodeChange1) is when VirtualPageSize="4".

The third image (SelfReference_CodeChange2) is when VirtualPageSize="2".

Am I missing something, or is there a bug here?

I get the same issues (bad counts, not all data loading) when attempting to use page size 10 on 21 parent records with 0 to 34 child records.

Hello Frank,

I can replicate the issue in here. I will discuss it with our developer teams first before can give a certain answer.

Regards,
Handy

Hello Frank,

This is a bug in our WebGrid. FYI, the paging should not take an effect for child row. It should only be applied for parent row. If you want still use Paging, I suggest you to use Classic Paging instead of VirtualLoad for now.

Regards,
Handy

I attempted to use classic paging, but the first two pages each take over 10 minutes to load. Unacceptable.

Hello,

It should not happen. Basically, it also should show time out when the response is too long. Perhaps, you can help us by giving the evidence or other details such as your code?

Regards,
Handy

Any plans for a fix for the initial bug?

Hello Frank, 

We are planning to release hotfixed in this month. I will set your issue as a high priority to our developer teams.

Regards,
Handy

Any update on this hotfix?

Hello Frank,

Due to another fixes priority, we decided to deliver the fix for your issue in the next month. We are truly sorry for this. We don't have enough time to include your fix in this month. But surely your fix has been included in our next month work plan. FYI, we are planning to release hotfixes regulary in each month to increase our support services.

Regards,
Handy

I look forward to it being fixed next month.

Is there a solution for this problem in the next hotfix release?

Is there a date this should be released?

Thanks.

Hello Frank,

This fix has been quequed in our hotfix priority in this month. The release is scheduled approximately within 23April.

Regards,
Handy

Checking on this fix - is it still scheduled to be in the 23 April release?

I have a release that may be delayed if this will be complete.

Hi Frank,

Ok. I will talk with our developer today. Please kindly let me know your date release. If it is possible, I will send you a nightly build.

Regards,
Handy

I will have a release scheduled on 4/26. If your code is released on 4/23, I will delay my release by up to two weeks to give time for testing the IS fix.

If you will not have the fix, I will release as scheduled - without the fix - and hope it makes it into your next release.

Hello Frank,

Please find the nightly build in below attahment. As I explained before, the paging only works in Parent, not child. You can show that Child rows are correcly loaded within this build.
Hope this helps.

Regards,
Handy