The issue is replicated only when a filtering operation is applied. For a grouping and sorting one it is not. This behavior is replicated in WPF only.

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

Can you add a grid-level option to hide any grouped columns automatically (rather than at the column level)?

I've tried creating a attached property behavior to do this (see attached), but it doesn't work well with auto-generated columns.

Would you please confirm the following bug? When selecting multiple rows of a *child* RadGridView, with multiple rows having optional nested RadGridViews, scrolling off the content of the WPF app causes the selection of those child grid rows to become unselected after scrolling back to the main selection of the child grid. If you must require a demo in order to get this feature fixed I might be able to extract one based our production application, but basically we have a Telerik grid control with nested grids that we want to maintain child selections on.

Thank you,
John Wilkins

Available in the R1 2017 SP1 Release.

Version 2016.3.1024.45 (from nuget packages, if that matters)
Adding a new row with the "Add new row" button and then clicking the row indicator results in an extra row. Demo: http://recordit.co/Nn8y2z2YpI

Available in the R1 2017 SP1 Release.

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 the R1 2017 SP1 Release.

Available in the R1 2017 SP1 Release.