Last Updated: 25 Apr 2016 08:09 by ADMIN
Created on: 02 Dec 2014 10:37
Category: PropertyGrid
Type: Feature Request
RadPropertyGrid not setting indexed properties
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.
Attached Files:
(Total attached files size should be smaller than 20mb. Allowed extensions: .zip, .rar, .jpg, .png, .gif)
Posted on: 16 Jul 2015 15:14
Hello Brian,
The development team reviewed the bug report back in April and it turned to be a more complicated case which was never supported. That is why they transferred it internally as a feature request. I also updated the feedback item to show this accordingly.
I am sorry to hear the issue causes you such troubles. We have the case logged in our backlog, however, for the time it is hard to tell when it will be implemented. You can follow the item to get notified once there is an update on it.
Posted on: 30 Jun 2015 17:51
Any update on this? Is it STILL causing us problems with no obvious workaround and my client is becoming increasingly agitated that I can't fix this problem.
Posted on: 22 Apr 2015 19:46
It has been almost 5 months now and my client is still asking me for a fix for this. Is a fix for this scheduled anytime soon?