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.

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

InvalidOperationException is thrown from the synchronizing of the pinnedItems state when the ItemsSource collection of RadGridView is changed by asynchronous operations.

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

Changing ItemsSource of the GridViewComboBoxColumn runtime leads to empty cells in that column.

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

The exception is fixed. To evaluate the IsReadOnlyBinding of the column, we do not use the built-in binding mechanism but a custom one. This custom binding mechanism is designed to use as a source only the default one which is the current item of the ItemsSource of RadGridView. This is the reason that the scenario where the default source of the binding is changed is not supported by design. 

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

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

A possible workaround is to predefine the CellTemplate of the column as well.

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

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

Provide an option to group a column which is based on an enum by the enum value, but display the DescriptionAttribute or DisplayNameAttribute if existing.
So many times you have sort/group a column by its value like 1,2,3 but display the Description like "Delivery", "Ready", "Pickup". Of course I could add a column to my class which presents the DescriptionAttribute, but then grouping/sorting is wrong: "Delivery", "Pickup", "Ready". It would by much easier if there is an option like "UseDescription". There is something similar with Teleriks "EnumDataSource" which IS using the Description or DisplayName so it should not be that hard to implement the same logic for RadGridView.