Skip to main content

Filter behavior with hierarchical field

Comments

4 comments

  • Dapfor Team

    Hi,

    Thank you for this post. We have identified the bug, related to graphical filters on 2nd, 3rd etc. hierarchical levels. It will be fixed in the next version. Note, non-graphical filters work as expected.

    We'll keep you informed when the patched grid will be available. We've included this fix into our planning and expect a new release the next week.

    Kind regards,

    Dapfor

     

    0
  • dx2003

    Hi Team!

     

    Thank you for you replay. I think, you have found all issues with filtering already.

    I would like just summarize the found problems:

    1) if grid have only one header (only one hierarchical level) the dropdown control was filled  with  the columns distinct values and "(All)" successfully.

    But the grid able to filter the string(!) values only.... If the column has other types, for example double on some enum, no filtering is possible with using the ValueEqualityDropdownFilter class.

    The issue is located in ValueEqualityDropdownFilter.Filter::IsFiltered(Row row).

    2) if the grid has more than one level  (the hierarchical levels > 1) , for example two, the dropdown control was filled  with the columns distinct values and "(All)" successfully. 

    But no any kind of filtering is possible: not for string data type and not for any other types of the column.
    Due to problems with the  hierarchical settings algorithm.

     

    BR,

    dx2003 

    0
  • Dapfor Team

    Thanks,

    We've already fixed all these bugs. Actually we are testing a new build. As soon as we complete necessary tests, we will release a revised version of the grid (normally this week).

    Best regards,

    Dapfor

    0
  • Dapfor Team

    Hi,

    We've released the .NetGrid v.2.8.3 without this bug.

    Best regards,

    Dapfor

    0

Please sign in to leave a comment.

Powered by Zendesk