UPDATE: The issue is reproduced with columns bound to other data types as well.

Workaround: reused the cell element like this:
CreateCellElement(Telerik.Windows.Controls.GridView.GridViewCell cell, object dataItem)
{
    var button = cell.Content as Button;
    . . .
 
    return button;
}

Not all of the FilteringControl elements have automation IDs. This fact prevents the proper usage of some automation frameworks.

InvalidOperationException, when sorting or filtering GridView and an observable immutable collection is used in a multithread application.

Available in LIB version 2017.1.213 , it will be also available in the R1 2017 SP1 Release.

Currently the new item's properties are validated before editing their values, which is not intuitive, especially for Required, MinLength etc. The correct behavior would suggest that validation should be applied only to "confirmed" property values.

To work this around you can set the EnableColumnGroupsVirtualization to False.

Alternatively you can change the FrozenColumnCount before adding the columns, and reset it once the process is done. For example:

gridTriffDetails.FrozenColumnCount = 0;
 
gridTriffDetails.Columns.Add(newColumn);
gridTriffDetails.Columns.Add(newColumn1);
gridTriffDetails.Columns.Add(newColumn2);
 
gridTriffDetails.FrozenColumnCount = 1;

the attached project displays a wpf radgridview bound to a list<person> via a viewmodel.
if you add a new row, enter some data, and tab through the values everything works fine.
if you add a new row,  enter some data, and click the rowheader of the new row, the grid displays incorrect values (see the attached screenshots.pdf)

Available in the R1 2017 SP1 Release.

Available in LIB version: 2017.2.703

A workaround for the issue is to apply a 1px top Margin.