Skip to content

Improving Grid filtering mechanism #8041

@kendo-bot

Description

@kendo-bot

Currently, when using the default Grid search functionality and the column filter menus, we observe the following:

  • When a column filter is applied first, using the Search feature afterward overrides the column filters, applying the search filter with the "contains" operator to the specified columns.
  • Conversely, when a search is performed first and then followed by a column filter, the grid generally functions as expected.

However, there’s a specific scenario where this does not work properly:

  • If a search is performed and then a column filter is applied to a column where the search criteria are relevant, the Grid returns no data.

For example:

  • After searching for "2018," the expected columns displayed in the filters (notably, the ContractNumber is among them).

Image

  • When a column filter is subsequently applied to ContractNumber (e.g., setting it to "2018-CR0018"), the Grid removes the ContractNumber from the search filters and adds the column filter with an "AND" operator. This setup returns no data because of the search filters and the "AND" operator.

Image

Expected Behavior and Alternative

This functionality behaves correctly in the Telerik UI for Blazor Grid component - the search and column filters are managed as separate objects.

Is it possible to enhance the Grid filtering similar to the Blazor Grid?

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions