Hello PPilev,

Using the latest 2011.2 controls.  Here is the method in the user control to convert the DataTable to an Ilist for the data selector and pivot grid:

public void SetFlatDatasource(DataTable dt)
{
    DynamicTypeBuilder typeBuilder = new DynamicTypeBuilder
    {
        DynamicAssemblyName = "MyAssembly",
        DynamicTypeName = "Pane"
    };

    IList properties = new List();

    foreach (DataColumn column in dt.Columns)
    {
        DynamicTypePropertyInfo propertyInfo = new DynamicTypePropertyInfo
        {
            PropertyName = column.ColumnName,
            PropertyType = column.DataType
        };
        properties.Add(propertyInfo);
    }

    Type dynamicType = typeBuilder.GenerateType(properties);
    Type listType = typeof(List<>);
    Type genericListType = listType.MakeGenericType(dynamicType);

    IList list = (IList)Activator.CreateInstance(genericListType);

    foreach (DataRow dataRow in dt.Rows)
    {
        object myDynamicInstance = Activator.CreateInstance(dynamicType);

        foreach (DataColumn column in dt.Columns)
        {
            PropertyInfo propertyVal = dynamicType.GetProperty(column.ColumnName);

            if (dataRow[column] != DBNull.Value)
            {
                propertyVal.SetValue(myDynamicInstance, dataRow[column], null);
            }
        }

        list.Add(myDynamicInstance);
    }

    FlatDataSource flatDataSource = new FlatDataSource()
    {
        ItemsSource = list,
        Cube = DataSourceBase.GenerateInitialCube("Pane"),
        // if you know the names of demensions you want to be in rows and columns you can define them here
        Columns = DataSourceBase.GenerateInitialItems("[Columns]"),
        Rows = DataSourceBase.GenerateInitialItems("[Row]"),
        Measures = DataSourceBase.GenerateInitialItems("Value")
    };

    dataSelector.DataSource = flatDataSource;
    pivotGrid.DataSource = flatDataSource;
}

When you say initialization, do you mean the xaml? If yes, how can we post xaml in this forum? I will say it does not contain anything special. AllowCompactLayout is set to True, Height and Width are set to Auto...there is really nothing noteworthy.

Simple question, should this control perform well with a row count of say 2,000 with 8 columns?

Thanks Plamen, I am scrambling to find examples that fit my environment.  All examples I see have pre-canned data model classes, something that is not real-world to us.  I need to see how I can setup hierarchies on my flatdatasource that is the product of a DataTable produced from a parameteratized SQL stored procedure call that is converted to a pivotgrid-friendly flatdatasource (the first method I posted here).  What is the best-practice for this?  How is it done?  Can you help? 

I cannot post data due to its confidential nature, but a datatype-only parallel would be something like Row groups: Chocolates > Brands > Brand Types > Product Names. Column groups: Distribution Regions > Distributors.  A measure might be "Pounds in stock".  There are no date \ time considerations.  The view is a single point in time; today.

Is it easy to quickly use this example to demonstrate how I can do this in the code-behind?  Do I need to define cube metadata or is the first method already doing that?

Again, it is my very first venture outside of Winforms and I feel like a total noob!  Thanks!

Hello Jaime,
Look at the attached sample and let me know of you have any further questions.

Plamen.

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!

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 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,