Thank you so much! I have spent so many hours for that. Thanks. I would like to give one suggestion. The way you guys designed this DataGrid is quite different from WPF ListView. It would be really great if we can re-use our existing skill instead of learning new thing. For example: Why Fileds? why not Column? How come AutoGenerateFields is under Setting? Why do I need to use Unbound field to bind the nested object? Why do we need to use CellPresenterSyle instead of ItemTemplate or DataTemplate? and etc... We are currently using Docking and floating window and we are really happy with that. We are thinking to use DataGrid too. We will probably buy it. We already bought Telerik control but we found that we have to workaround a lot of things in order to make it work.

I can comment on part of your question. 

I believe we used "fields" instead of "columns" because these entities may not visually appear as a "column" in the XamDataGrid.  Likewise, we use "records" instead of "rows" since these might not visually appear as "rows" on the screen.  For instance, one record might appear as four separate rows, with two fields per column and another field that spans both columns.

We indeed try to set up our controls so that knowledge of similar constructions can be re-used.  When needed, such as when terminiology would be imprecise in the context of the control or when the existing "similar construction" isn't able to handle what we want the control to accomplish, we'll deviate from this approach.