New to Telerik UI for ASP.NET AJAX? Download free 30-day trial


In complex scenarios, where master pages and user controls are utilized and more than one RadPersistenceManager is required in order to handle all the controls which state should be persisted, RadPersistenceManagerProxy should be used in the context pages / user controls.

RadPersistenceManagerProxy offers a declarative (design-time) approach to configure PersistenceSettings in the context of a NamingContainer. This helper control copies the exact same RadPersistenceManager designer configuration.

<telerik:RadPersistenceManagerProxy ID="RadPersistenceManagerProxy1" runat="server">
        <telerik:PersistenceSetting ControlID="RadListView1" />
        <telerik:PersistenceSetting ControlID="RadGrid1" />
        <telerik:PersistenceSetting ControlID="RadCalendar1" />
        <telerik:PersistenceSetting ControlID="RadCalendar2" />

In scenarios where persistence manager proxies are used there may be cases when two controls have identical IDs. An example for such a scenario would be, if you have a master page and two content pages and each content page contains a RadGrid with ID="RadGrid1". The problem is that if you once save the settings for the grid on the first page and then load them on the other page, the settings will be applied to the second grid, regardless of the fact that the control is not the same.

To prevent this behavior you can set the UniqueKey property of the RadPersistenceManagerProxy, that will help you to distinguish both grids.

The value of UniqueKey must be unique and should be set to all proxies.

In this article