Regarding your first question: You are correct in your observation that the filter options could be limited only on the client. However, the described approach is required because RadFilter
uses one RadMenu
for all filter options and does not have distinction for individual filter items in order to limit the options individually.
Regarding your second question: You could achieve your scenario by creating your own custom field editor in which you could place any control you want and then use the query provider ExpressionEvaluated
delegate which is available in our latest official release and could help you in altering a query provider result string. You could take a look at the demos and help articles below which describe how to implement the things described above.
Regarding your third question: In the latest release we have implemented couple of new methods for working with filter expression items that are documented in the article below. The methods involved are -
Regarding the XML representation: I can ensure you I have contacted our dev team and notified them for your suggestions. Note that decisions for implementing a particular functionality is based on the customer demand rates and the control needs.
If you want to get updates on new releases, tips and tricks and sneak peeks at our product labs directly from the developers working on the RadControls for ASP.NET AJAX, subscribe to the blog feed