我无法发现如何启用Persistence Framework Manager来检查和序列化详细信息表中的列数据(显示/顺序/等)。 我有详细信息表的父RadGrid正确保存列显示/顺序,但它不会自动序列化子GridViewTable。 根据http://www.telerik.com/help/aspnet-ajax/persistence-framework-supported-controls.html,Persistence Framework支持GridTableViews。
任何人都可以了解我如何将其添加到我的持久性管理器中? 似乎GridTableView不能从ASPX页面分配ID,因此,我无法以我的RadGrid方式将其添加到我的经理。
谢谢,
AlexK
更新:我试图通过在Page_Init事件上添加以下内容后面的代码添加详细信息表...
PersistenceManager.PersistenceSettings.AddSetting(ParentRadGrid.MasterTableView.DetailTables(0))这引发了一个PersistenceFrameworkException ,其中详细说明The control of Telerik.Web.UI.GridTableView could not be persisted. Please review the online documetation for the supported controls. The control of Telerik.Web.UI.GridTableView could not be persisted. Please review the online documetation for the supported controls.
I am unable to discover how you can enable Persistence Framework Manager to check for and serialize the column data (display/order/ect) inside of a Detail Table. I have the Detail Table's parent RadGrid properly saving column display/order, but it is not automatically serializing the child GridViewTable. According to http://www.telerik.com/help/aspnet-ajax/persistence-framework-supported-controls.html, GridTableViews are supported by Persistence Framework.
Could anyone shed some light on how I may add this to my Persistence Manager? It does not seem that GridTableViewcan be assigned an ID from the ASPX page, thus, I have not been able to add it to my manager in the way in which I did my RadGrid.
Thank you,
AlexK
UPDATE: I attempted to add the Detail Table via the code behind by adding the following on the Page_Init event...
PersistenceManager.PersistenceSettings.AddSetting(ParentRadGrid.MasterTableView.DetailTables(0))This threw a PersistenceFrameworkException with the details stating The control of Telerik.Web.UI.GridTableView could not be persisted. Please review the online documetation for the supported controls.
最满意答案
只支持MasterTableView ,我问过,DetailTables不支持。 文档是固定的:)
Only the MasterTableView is supported, I have asked, DetailTables are not. The documentation is to be fixed :)
更多推荐
发布评论