Wired my first xamPivotGrid into a user control that is consumed by a winforms app. Borrowed a method from these forums that takes a DataTable and dynamically all columns and rows to an Ilist, which is set to the pivotDataSelector and pivotGrid's DataSource.
My application loads at a cost of 90,512k. I load the data into the pivot grid and it hit 96,180. The DataTable contains 1,216 rows and 8 columns. Dragging just 3 columns to the Rows box drives the application memory cost to ~1,650,227k before the application throws a System.OutOfMemory exception.
As my first venture, I am obviously missing something critical here, but not finding much and not really sure what to look for. Feeling additional paing because I am under the gun to get something working and performing by next Monday. I have seen code examples that set hierarchies and a whole bunch of other things that do not seem very appealing because of hard-coded column names, etc., and not even sure these would help me?
In short, I guess what I need is something like "Jaime, if your clients will be working with large (is my example above large???) data tables, then you need to do this..."
I will seriously cry if I can't get this to perform well. We purchased the IG Ultimate just for the pivot grid and time is running out for me... perhaps literally at that!
Many thanks!!! -Jaime
Hello Jaime,
Currently we don’t provide an option to separate the topics from a forum thread, still if you want you can post the question as a new topic and I will copy the answer that Mircho provided for you.
Hello Mircho,
Works exactly how I had hoped! Many thanks. Unfortunately I did a bad thing and have asked questions within this post not related to the main point of the post. This is valuable lesson for other users that I fear will remain lost here.
Is there a way to separate this question and your answer into another post for the benefit of the community?
Thanks again!
Jaime
Hi JaimeZ,
Members count shows you how many hierarchies you have in the row tuple. So this check, r.Tuple.Members.Count == 1, shows that there is only one hierarchy in the row. What i understood is that you want to hide all totals that are aggregating only one item. What i can offer is this one:
foreach (PivotDataRow r in pivotGrid.DataRows) { foreach (var member in r.Tuple.Members) { if (r.IsTotal & member.ChildCount == 1) { r.IsVisible = false; } } }
Hope this will resolve the issue.
Regards,
M. Yovchev
Hello again,
I was not able to achieve the hiding of row totals only when the members being totalled are greater than a count of 1. This would be a great feature for your pivot grid. Having row totals only where there is more than one data element to total would mean more data to review on screen and less noise. I tried the following code but it hides all row totals in the heirarchy being expanded, not just ones where there is only one member to total:
private void pivotGrid_LayoutLoaded(object sender, EventArgs e) { foreach (PivotDataRow r in pivotGrid.DataRows) { if (r.IsTotal & r.Tuple.Members.Count == 1) { r.IsVisible = false; } } }
It seems that Tuple.Members.Count is always one, which I assume is the root element of each hierarchy being expanded? I was hoping for a way to get a count of what is being totaled, which yet may be possible?
Hello Elena,
Plamen has answers a few secondary questions, so those are issues are solved, however the main topic of this post deals with running out of memory when dragging data items from the xamPivotDataSelector into pivot grid rows. The data is from a DataTable that is converted into a FlatDataSource. There is an open support case for this, so maybe it would be good to leave this post open until the issue is resolved via a service release or other solution?
Thank you for the thread link!