Hello Dave,

I am not completely sure if this is the correct behavior of the XamDataGrid. If you have set AllowGroupBy to false globally and then explicitly just set AllowGroupBy only to Type, Category 1 and Category 2 , then this is expected, as the Name would have AllowGroupBy false and will disappear.

I believe I did something like this in the forum, but cannot seem to find it right now, but :

Creating a style for the GroupByFieldLabel and using a DataTrigger with Binding Field.Name and Value Name (in your case) and setting the Visibility property to Collapsed would do the trick.

<Style TargetType="{x:Type igDP:GroupByFieldLabel}">

<Style.Triggers>

<DataTrigger Binding="{Binding Field.Name}" Value="Name">

<Setter Property="Visibility" Value="Collapsed"/>

</DataTrigger>

</Style.Triggers>

</Style>

I've added your style to "Doc1.xaml", for the "department" field (it programatically groups by this field when loaded).  The idea being we want to force the department grouping, users should be able to apply additional groupings on top of this one, but they should not be able to remove the department grouping at all.

The style does have the effect of hiding the "department" LabelPresenter when in the group by area, but it also has a couple of strange side effects.  The style of any additional LabelPresenters in the group by area loose their background and the style of all the standard LabelPresenters in the header row get messed up:

I'm really not sure what's going on here as that style should surely only be affecting the department field!?

Dave