By default RadPropertyGrid loads its nested properties definitions on demand, when auto-generated PropertyDefinitions are used. RadPropertyGrid mainly targets scenarios, where an item's properties and their nested properties are displayed and modified. So, if that is your case, it should be a viable choice. On the other hand, if you are aiming to process a collection of items which have hierarchical dependencies to other items RadTreeView or RadTreeListView (or RadGridView) should be much more convenient controls. RadPropertyGrid can also handle custom hierarchies with its unbound mode feature, but it may require a lot of additional customizations for ceratin scenarios. Would you please provide some additional info about the structure of your data and the overall UX that you aim to achieve, so that we could more precisely
discuss with you the choice of an appropriate control.
the Telerik team