Available in LIB version 2018.1.122, it will be also available in the R1 2018 SP Release.

As of R1 2018 the GetCellContent method is no longer used for exporting a custom column content. Instead, the GetExportCellContent one of GridViewBoundColumnBase needs to be overriden.

Currently, RadGridView's data engine relies on TypeDescriptor.GetProperties, when resolving the set of properties accessible through a certain type. Apparently, this API hides the properteis from the interface, as they are not accessible throught the concrete type.

Available in LIB version 2017.3.1204, it will be also available in the R1 2018 Release.

Similar to the one in RadPivotGrid:
https://docs.telerik.com/devtools/wpf/controls/radpivotgrid/features/localdatasourceprovider/serialization

And here is an online demo:
https://demos.telerik.com/silverlight/#PivotGrid/Serialization

Available in LIB version 2017.3.1127, it will be also available in the R1 2018 Release.

Available in LIB version 2017.3.1127, it will be also available in the R1 2018 Release.

When applying VQCV with custom IEnumerable as a source to the ItemsSource of the grid and filters grid through filtering control, ExportToXlsx exports wrong items.

Available in LIB version 2017.3.1127, it will be also available in the R1 2018 Release.

Added the CanUserSearchInHiddenColumns property which indicates whether users can search for content in hidden columns. The property is available with our 2017.3.1127 internal build.

Available in LIB version 2017.3.1113, it will be also available in the R1 2018 Release.

When setting the VirtualItemCount on refreshing the data source, the scrollbar jumps to the top. If the VirtualItemCount is initially set, the behavior is not reproduced. The workaround is to use the scrolling mechanism of the control and scroll back to the desired item.

In an application, I bind a DataTable with many rows to a RadGridView. As soon as, the datatable is binded, I see the memory needed by the application growing. The problem is that the binding is done each time the content of the DataTable is changing. It seems that the memory is never cleared and keep growing until a MemoryException is thrown. This does not appear with a WPF standard GridView. Do you know why ?

Currently, you can use only the predefined one - IsEqual, IsNotEqual, etc. Add an option to create operators that execute custom filtering action. Also, add support for modifying the default operators.