When saveing / loading large views in XamPivotGrid, loading takes very, very long since it has to expand every member one by one. Even disconnecting the datasource from the control (setting grid's datasource to null) doesn't speed up the process. We have pretty large dimensions with 100+ members, so the average loading time is about 3 minutes per view!
And one more question: is it possible to disable the filter behavior where expanding a member in the filter also expands it in the grid? If you use a filter on a 2nd level hierarchy your expanded states get lost (all will be expanded / collapsed).
BR
Daniel
Hello,
We have shipped out a new service release where your issue is resolved. I'd be glad to find out if you had tested it out and if it had met your requirements.
You can download the Service Releases by logging to our web site and going to Account\My Keys and Downloads page.
Thank you for using Infragistics Components.
Sincerely,ZhivkoAssociate Software Developer
do you have any news on this?
We really need this fixed since it renders our application unusable...
Regards
Hello Daniel,
I have logged this behavior with our developers in our tracking system, with an issue ID of 203258. I have also created a support ticket on your behalf with number CAS-158325-Y3F0S3 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.
As I told you, there need to be many (100+) expandable members in the grid (see attached views). Sure they contain a large dataset, but loading it takes way too long in comparisson to building it manually. The problem seems to be that every member has to be expanded one by one, while an amount of members can be expanded at once manually.
We were able to reproduce the behaviour by utilizing multiple dimensions on one axis and expanding every available member (see attachment). Since our customers are using dimensions with more than 100 expandable items, having that many items on one axis is a common occurence.
Thank you for your post!
I have been looking into it and have created a small sample application in order to test the functionality you have described. Using the sample application I was not able to reproduce the issue.
I am attaching the sample application for your reference. Would you please modify it with the functionality you are using, so it reproduces the issue? This way I would be able to further investigate this matter for you.
Looking forward to hearing from you.