Hello Plamen,

I'm operating with one Hierarchy with 4 Levels beneath, i attached 2 screenshots to illustrate what i'm doing.

The Code you provided me with didn't change that behaviour - As soon as RefreshGrid is called the Application stops.

BR,

Daniel

####

Hi Plamen,

unfortunately it's a customer's environment so i have no impact on which version of .NET is installed. 

BR,

Daniel

Hello,

I have logged this behavior with our developers in our tracking system, with an issue ID of 144614. The next step will be for a developer to review my investigation and confirm my findings or to offer a fix, or other resolution. I will leave this case open and update you with this information after the review. You can also continue to send updates to this case at any time.  I have also created a support ticket on your behalf with number CAS-117816-B7R7P1 in order to link the development issue to it so that you are automatically updated when a Service Release containing your fix is available for download.

You can view the status of all development issues connected to this case from the "Development Issues" tab, when viewing this case on the "My Support Requests" page of our website.

Best regards,
Plamen

Hello,

I'm facing exactly the same issue. This seems to be bug which came with Version 13.1 because with the XamPivotGrid in Version 12.2 same function works fine.

To investigate the problem I polled the IsBusy-Flag and can see that this flag is always set to true and runs in an infinit loop.

Can you commit that there is a bug in your control and can you tell me when it is fixed or do have a workaround?

Task expandTask = ( (DataSourceBase)pivotGrid.DataSource ).ExpandToLevelAsync(filterViewModel,filterViewModel.Hierarchy.Levels.Count -1);

                    expandTask.Wait();

                    pivotGrid.DataSource.RefreshGrid();

while (pivotGrid.DataSource.IsBusy)

{

Thread.Sleep(100);

}

Hello mwicke,

I have been looking into your enquiry and you don’t really seem to have the same issue, since in your code:

expandtTask.Wait();

blocks the main thread before the task has actually started. This is because the Task, that is returned, requires some time to gather metadata before actually starting the expansion. I have tested your code against both 12.2 and 13.1’s latest builds and in both cases your Wait() method is block the main thread, which if you debug will never get you to the RefreshGrid method nor to IsBusy checksum.

In order to execute the refresh I can suggest following Plamen’s suggestion:

IFilterViewModel filterViewModel = (IFilterViewModel)dataSource.Rows[0];

Task expandTask1 = dataSource.ExpandToLevelAsync(filterViewModel, filterViewModel.Hierarchy.Levels.Count - 1);

expandTask1.ContinueWith(t => dataSource.RefreshGrid(), TaskContinuationOptions.ExecuteSynchronously);

or a similar approach:

IFilterViewModel filterViewModel = (IFilterViewModel)dataSource.Rows[0];

Task expandTask = dataSource.ExpandToLevelAsync(filterViewModel, filterViewModel.Hierarchy.Levels.Count - 1);

expandTask.ContinueWith(

    t => dataSource.RefreshGrid(),

    TaskScheduler.FromCurrentSynchronizationContext());

Please let us know if you require any further clarification on the matter.

Hello Petar,

sorry for my misleading sample. This was just to demonstrate that even if you wait for the task (what makes this asynchron task kind of synchron) the RefreshGrid() is causing the program to freeze.

I've now tried your suggestions but they also have the same effect. Here is my original code, an extension method for the XamPivotGrid which I'm calling in my ViewModel classes not in code behind of the view:

 
public static void ExpandAllHeaders(this XamPivotGrid pivotGrid, Action callback = null)

{

var filterViewModels = pivotGrid.DataSource.Rows.Concat(pivotGrid.DataSource.Columns).Where(fvm => fvm is IFilterViewModel).ToList();

for (int i = 0; i < filterViewModels.Count; i++)

{

var filterViewModel = filterViewModels[i] as IFilterViewModel;

if (filterViewModel == null)

return;

if (i == filterViewModels.Count - 1)

{

EventHandler<ResultChangedEventArgs> handler = null;

handler = (sender, e) =>

{

pivotGrid.DataSource.ResultChanged -= handler;

if (callback != null)

callback();

};

pivotGrid.DataSource.ResultChanged += handler;

( (DataSourceBase)pivotGrid.DataSource ).ExpandToLevelAsync(filterViewModel, filterViewModel.Hierarchy.Levels.Count - 1)

.ContinueWith(t => { pivotGrid.DataSource.RefreshGrid(); }, System.Threading.Tasks.TaskContinuationOptions.ExecuteSynchronously);

}

else

{

( (

DataSourceBase)pivotGrid.DataSource ).ExpandToLevelAsync(filterViewModel, filterViewModel.Hierarchy.Levels.Count - 1);

}

}

}

Hello mwicke, 

I have been looking into this for you and created a test sample to your specification (Pivot_tasks.zip) running under version 13.1. When I run it and press the expand button first the top XamPivotGrid’s Columns expand and then the bottom XamPivotGrid’s Columns expand too. I have attached the sample for your reference please let me know, if you can reproduce the behavior you described using it, or please modify it so it does. 

Looking forward to hearing from you.

No answer?

Hello Plamen,

I tried your suggestion but this also doesn't work. The problem is that RefreshGrid is called but freezes the application before ResultChanged event is fired.

I figured out how to reproduce the behavior. If you call my ExpandAll function with two pivot grids one after another the expanding works:

MyXamPivotGrid1.ExpandAll();

MyXamPivotGrid2.ExpandAll();

But if I'm using the callback as shown below it leads to the described freezing error:

            MyXamPivotGrid1.ExpandAllHeaders(

                () => MyXamPivotGrid2.ExpandAllHeaders());

But my Problem is that I have to use the callbacks to know when the expansion is finished and then start an excel export of the grids.

It would be nice if you could try to reproduce this with an own sample (Two filled pivot grids expanding with my function in callback).

As mentioned all worked before I upgraded to the new NetAdvantage Version 13.1. so could it be that your development team maybe changed something in the RefreshGrid method?

Regards

Hello,

When you have to expand multiple hierarchies my suggestion is to collect all your task objects in a list and call RefreshGrid() once all tasks are completed:

Task.Factory.ContinueWhenAll(tasks.ToArray(),

    t => dataSource.RefreshGrid(), TaskContinuationOptions.ExecuteSynchronously);

Regards,
Plamen.