Problem with FilterDescriptor in Q1 2013

3 posts, 0 answers
  1. Renate
    Renate avatar
    4 posts
    Member since:
    Nov 2011

    Posted 13 Mar 2013 Link to this post


    I have a problem with different behavior of FilterDescriptor in Q1 2013 (upgraded from Q1 2012).
    I want to filter out all rows where 2 columns have a value of string.Empty and set the filter like this:

    CompositeFilterDescriptor cfd = new CompositeFilterDescriptor();

    FilterDescriptor fd1 = new FilterDescriptor("Anlage", FilterOperator.IsNotEqualTo, "");

    FilterDescriptor fd2 = new FilterDescriptor("Bestellung", FilterOperator.IsNotEqualTo, "");

    cfd.LogicalOperator = FilterLogicalOperator.Or;

    In Q1 2012 this resulted in:
    CompositeGridFilter, Expression: (Anlage <> '' OR Bestellung <> '')    

    In Q1 2013 the expression now is:
    (NOT (Anlage IS NULL) OR NOT (Bestellung IS NULL))

    which is not what I want!

    Is there any way around this?

    Thanks a lot in advance


  2. Julian Benkov
    Julian Benkov avatar
    1135 posts

    Posted 15 Mar 2013 Link to this post

    Hi Renate,

    Thank you for writing.

    In the last release we introduced fixes and improvements to the 
    Null value support in filtering operation. I have tested your filtering scenario and I found that the introduced changes caused a regression on the filtering operation when empty string value is used. The issue is already resolved and fix will be included in the Q1 2013 SP1 release, planed to be available for download by the end of the month.

    Thank you for the report. Your Telerik points have been updated.

    All the best,
    Julian Benkov
    the Telerik team
    WinForms Q1 2013 boasts PivotGrid, PDF Viewer, Chart enhancements and more. Check out all of the latest highlights.
  3. Renate
    Renate avatar
    4 posts
    Member since:
    Nov 2011

    Posted 15 Mar 2013 Link to this post

    Hi Julian,

    thank you for the reply!
Back to Top