Gergana,

I have a IEnumerable<DataType> where the DataType has upto 20 properties. The IEnumerable has between 10 to 1000 items. I'm grouping the data by upto 4 properties of the DataType. This is fine when there is 1000+ items, all the groups make sense. However when there are only 10 items, 2 of the groups are not required. So I would like to examine the groupings and if the group only contains one group, then remove, turn off or set a setting that stops XamDataGrid to not allow groups with only one group.

 Sorry just realised that I pasted the wrong code snippet in my original post.

I'm doing it just before I'm doing the summaries with this:

if (attributes.Any(attribute => attribute.GroupBy))
{
    if (!XamDataGrid.Resources.Contains("ColourKey"))
    {
        var datatype = typeof (GroupByRecordPresenter);
        var style = new Style(datatype);
        style.Resources.Add(new ComponentResourceKey(typeof (XamDataGrid), "LabelHighlight"), new SolidColorBrush(Colors.Transparent));
        style.Resources.Add(new ComponentResourceKey(typeof (XamDataGrid), "LabelBackground"), new SolidColorBrush(Colors.Transparent));
       
        foreach (var source in attributes.Where(attribute => attribute.GroupBy).OrderBy(attribute => attribute.Order))
        {
            var brush = new LinearGradientBrush() { Opacity = 0.5, StartPoint = new Point(0.5,0), EndPoint = new Point(0.5,1)};
            brush.GradientStops.Add(new GradientStop(Colors.Snow, 0));
            if (source.ColourBinding)
            {
                var stop = new GradientStop(source.ColourCodeFinish, 0.9);
                var binding = new Binding("ChildRecords[0].DataItem." +
                        attributes.FirstOrDefault(attribute => attribute.ColourBound).PropertyName);
                BindingOperations.SetBinding(stop, GradientStop.ColorProperty, binding);
                brush.GradientStops.Add(stop);
            }
            else
            {
                brush.GradientStops.Add(new GradientStop(source.ColourCodeStart, 0.1));
                brush.GradientStops.Add(new GradientStop(source.ColourCodeFinish, 0.9));
            }
            e.FieldLayout.SortedFields.Add(new FieldSortDescription(source.PropertyName,
                ListSortDirection.Ascending, true));
          
            brush.GradientStops.Add(new GradientStop(Colors.Snow, 1));
            var trigger = new DataTrigger() {Value = source.PropertyName};
            trigger.Binding = new Binding("GroupByField.Name") { BindsDirectlyToSource = true };
            trigger.Setters.Add(new Setter(BackgroundProperty, brush));
            style.Triggers.Add(trigger);

        }
        XamDataGrid.Resources.Add("ColourKey", style);
    }
   
    var statbinding = new Binding()
    {
        Source = XamDataGrid.Resources["ColourKey"],
        BindsDirectlyToSource = true
    };
    BindingOperations.SetBinding(XamDataGrid.FieldSettings, FieldSettings.GroupByRecordPresenterStyleProperty, statbinding);
}

Hello ahrensd,

Thank you for the provided coded snippet.

I have been looking into and I have some questions for you. Do you want when there is only one item in a Group, this Group to not be shown or Summaries for this Group to be not applied?

Looking forward to hearing from you.

I don't want the grouping for that field to be applied.

here is a screen shot, it turns out very messy with the grouping not doing anything but add confusion. would be great if the control could deal with this.

Hello ahrensd,

I am just checking if you have any further questions on this matter. Please do not hesitate to let me know if you do.

Have used this code for my application and it doesn't work when you programmiclly add the FieldSortDescription's in the FieldLayoutInitialized.

Close but doesn't call igDataGrid_Grouping  in this case.

Thanks for your time Gergana,

Your modified code didn't quite cut it, but did put me on the right track, which I would never of found without your help.

After some further alterations I have something that behaves how I wanted.

Any improvements welcomed, how about putting the functionality directly in the library?

Regards David