I'm having a problem with the RadPropertyGrid when bound to an indexed property. Getting the property works fine, but after changing the field, the setter never gets called.

 Attached is a simple test program. This program has a RadPropertyGrid bound to a simple string property and an indexed property. These same two properties are also bound to a TextBox.

 Notice that when the values in the TextBoxes are changed, the debug output shows that the setters are called and the values displayed in the RadPropertyGrid are properly updated.

 When the simple string is changed in the RadPropertyGrid, the debug output shows that the setter is called and the value displayed in the TextBox is properly updated.

 But, when the indexed property is changed in the RadPropertyGrid, the debug output does not show the setter getting called and the value displayed in the TextBox does not get updated.

*** The support for collection indexer binding will be available with R2 2016.

Provide support for Editor Attribute.

InvalidCastException is thrown when binding PropertyGrid.Item to collection. The exception is thrown in \\Core\Data\Extensions\FuncExtensions.cs. 

Unable to cast object of type 'System.Collections.Generic.List`1[System.Windows.Window]' to type 'Telerik.Windows.Controls.Data.PropertyGrid.PropertySet'.

Resolved with LIB version 2014.1.317

RadPropertyGrid's Description Panel Resizing/Visual Studio like behavior

Research the opportunity to add support for TypeConverter on class.

Available in the 2017 R1 Release (2017.1.117).

Currently, the control allows you to search only for fields that have been expanded already. If a parent field was never expanded, the search won't look for its children.

Allow searching in not expanded fields.

So far only IDataErrorInfo and exception based validation is supported. RadGridView already supports INotifyDataErrorInfo, it's time for RadPropertyGrid.

Behind the scene we need to update any changes made in the property grid, in a SQL Server database, too. With our current implementation we fire a database request if a property is edited in the property grid. This is fine if only one entity has been selected. If more than one entity has been selected (ProperytSetMode “Intersection”) a database request is fired for each entity if a property is edited. This is not very performant for us.
We need an event like “EditEnded” to figure out when the PropertySetViewModel has updated all ViewModels. Then we are able to updated the necessary changes in the database in a single call. 

Available in the 2017 R1 Release (2017.1.117).

This feature will be available with Q3 2014. User can specify the criteria used for filtering. All he/she needs to do is to override IsFiltered property of PropertyDefinition and set the his/her logic there.

Should be resolved with lib version 2014.3.1124.

GetStandardValuesSupported and GetStandardValues methods of a type converter are not called.

Available in the 2017 R1 Release (2017.1.117).

Foreground defined within PropertyGridField's Label Style is not applied in Expression_Dark theme.

The editor of nullable properties with non-matching values does not display the default value for this type(null) using PropertySets.


Available in LIB version: 2017.2.515

Nullable properties with non-matching values are not updated after clearing the entire text of the field(PropertySets).


Available in LIB version: 2017.2.515