Hi,

In our application we allow users to save customizations they have made to a grid to a database. The issue we have is that the fields in that grid are always changing and whenever a field is dropped from the field layout definition this then breaks all the saved customizations. We either have to manually go in and tweak all the XML in the database or we have to ask the users to create their saved view again. As you can imagine, neither is a particularly satisfying solution.

Is there a way we can make LoadCustomizations not fall over when a column no longer exists? And if not, can this be raised as a feature request to allow the method to ignore missing fields.

(Let me know if you require a sample attachment but it is quite simple to recreate yourself. Create a grid with two fields and extend the column width of both. Save the customization xml. Then delete one of the field definitions, reload the app and attempt to load the customization xml and it will not apply the column width to the column that does still exist).

thanks,

Karan