So, if you are willing to go with this approach (decide where to put spaces depending on the record's type) you have to find another way to distinguish where your table ends. 

There is no straightforward way of doing this as all the different types of record are in the same panel, or at least I cannot find any.

What I was able to come up with is to use the AddNewRecord. You can set its location to OnBottom and this will be your bottom marker.

If you do not use it, you can set its Opacity, IsHitTestVisible or Visibility in order to hide it. Here is the modified DataRecordPresenter style:

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

                        <Setter Property="Margin" Value="{Binding Converter={StaticResource conv1}}"/>

                        <Style.Triggers>

                            <Trigger Property="IsAddRecord" Value="True">

                                <Setter Property="Margin" Value="0,20,0,0"/>

                                <Setter Property="Opacity" Value="0" />

                                <Setter Property="IsHitTestVisible" Value="false"/>

                            </Trigger>

                        </Style.Triggers>

                    </Style> 

On the screenshot should be the actual result.

Note that the bottom space is bigger that the top, because there is a record there, so you could reduce the margin on the AddNewRecord.

Hi Alex,

That's an interesting idea and the explicit example doesn't quite achieve what I want but the general approach might. Consider the following would be what I'm looking for:

- ALFKI          Alfreds Futterkiste      Maria Anders

.......+ CustomerCustomerDemos

< BIG SPACE HERE > 

.......- Orders

..............10643          Alfki

..............10692          Alfki

..............10835          Alfki

..............10952          Alfki

..............11011          Alfki

< BIG SPACE HERE > 

+ ANATR          Ana Trujillo Emparec      Ana Trujillo

+ ANTON         Antonio Moreno Tac        Antonio Moreno

Let me know what you think.

Thanks!

Hello,

There seems to be a way around this - using the new not nested panels. This time you would not target the ExpandableFieldRecordPresenter but the DataRecordPresenter and especially the HeaderRecord, which is always the first one of the field layout ( and below what used to be the nesting ExpandableFieldRecordPresenter)

So to make this work, you can create a style for the DataRecordPresenter and a Converter, like this:

<local:MyConverter1 x:Key="conv1"/>

...

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

<Setter Property="Margin" Value="{Binding Converter={StaticResource conv1}}"/>

</Style>

What the Converter does is to see if the record is a HeaderRecord and not in the default layout (because you probably do not want a margin there):

public object Convert(object value, Type targetType, object parameter, System.Globalization.CultureInfo culture)

        {

            Record r = (Record)value;

            if (r == null)

                return Binding.DoNothing;

            if (r.RecordType == RecordType.HeaderRecord && !r.FieldLayout.IsDefault)

                return new Thickness(0, 20, 0, 0);

            else return Binding.DoNothing;

        }

I am attaching of screenshot with the effect you should get. That is what you are trying to achieve, right?

I wouldn't think so. We do regression testing using both modes. The nested panel mode is fully supported.

Thank you Joe. One of the reason I upgraded was to take advantage of bug fixes. If I use the nest panels option with the newer XamDataGrid, will any of the bug fixes be negated?