Thanks for the response Antonio. I had not found the link to what properties of what controls the Persistance Framework can serialize. I had looked at the Persistance demo using the RadPivotGrid
and had made the assumption that all the controls were being saved/restored. So referencing the demo sample for the RadPivotGrid:
does this mean that to save/restore a layout constructed in this demo it would be necessary to write custom code that walks the filter fields, row fields, column fields, aggregate fields and a custom process to save/restore all or only that the filter fields needs to be custom coded and the Persistence Framework will handle the rest (I don't see all the other field properties listed in the RadPivotGrid section of the Persistance Framework reference) ?
In a nutshell I need to be able to reproduce the functionality of the OLAP RadPivotGrid demo with a variable data source and with the addition of full save/restore capability of layout and filter, row, column and aggregate fields.