Excellent work with this new filtering ability guys. This is a very good feature that will dramatically improve the usefulness of the XamDataGrid. Definitely beats that one I had slapped together. Now, when saving customization, do you guys also save the current filter settings?
Speaking about features, one more feature that would be very useful is the ability to show and hide fields as well as save this customization.
Klaus
Hello Ramajayam,
I Have been looking into this and it is because the links were given in May 2009 and have already been changed with the update ones for the new versions. You can use their equivalents from the online documentation: http://help.infragistics.com/Help/NetAdvantage/WPF/2012.1/CLR4.0/html/xamDataPresenter_Save_Field_Customizations.html and http://help.infragistics.com/Help/NetAdvantage/WPF/2012.1/CLR4.0/html/xamDataPresenter_Load_Field_Customizations.html
Hope this helps. Please let me know if you need any further assistance on the matter.
The given links are not working!!!
You can see more information about loading and saving customizations of the DataPresenter in our help on the links below:
save field customizations
load field customizations
In 9.1, settings regarding RecordFiltering are also saved.
I believe your case is not just the same, but it is ok as long as it is loading settings correctly and the error is not showing up.
hi, correction in previous post : fieldList may NOT be null, so now I pass in a String.Empty, and the load error is gone, only I would like to know if it is ok to pass in String.empty.
We use the LoadCustomizations(string) methid, and pass in a string that is the result of the serialization of a class, so we can define the settings in xaml :
So in that intermedate class we use for serialization, I added a property fieldList, which I initialize in the constructor. Now the settings load just fine. Hope it is clear enough
Hello,
The field list is just enumeration of the names of the fields in the field layout.
Could you provide more information about your fields, fieldlayouts and how you load the saved settings.
Does this error occur only when you load from the previous version or everytime you load the settings?
Regards,
Alex.