search

IgniteUI / igniteui-angular

Ignite UI for Angular is a complete library of Angular-native, Material-based Angular UI components with the fastest grids and charts, Pivot Grid, Dock Manager, Hierarchical Grid, and more.
https://www.infragistics.com/products/ignite-ui-angular
Other
571 stars 160 forks source link

Advanced filtering window displays no filters after data change #14595

Closed georgianastasov closed 3 weeks ago

georgianastasov commented 1 month ago

Description

When using a grid with advanced filtering enabled (allowAdvancedFiltering set to true) and auto-generated columns (autoGenerate set to true), an issue occurs when filters are applied to columns and then the grid's data source is updated. Specifically, when the grid's data source is changed, resulting in new columns being generated, the advanced filtering interface fails to display the filters that were previously applied. This leads to confusion as the applied filters seem to be lost, and users cannot see or adjust them for the new data.

Steps to reproduce

  1. Create a grid with allowAdvancedFiltering and autoGenerate set to true and enable advanced filtering.
  2. Apply a filter to one of the columns using the advanced filtering window.
  3. Change the grid's data source to a new dataset, resulting in different columns.
  4. Notice that the new data does not display as expected because the previous filter is still applied.
  5. Open the advanced filtering window to view the applied filters.

Result

After following the steps, the advanced filtering window opens but displays no filters, even though the grid still indicates that a filter is applied. This results in confusion as the user cannot see or modify the filters applied to the previous data.

Expected result

After changing the data source and applying new filters, the advanced filtering window should either:

Retain and display the filters applied to the previous data, or Notify the user that the applied filters have been forgotten or become invalid due to the data change.

Attachments

a

georgianastasov commented 3 weeks ago

After discussing this issue with the architects and design team, we've decided that it will not be treated as a bug fix or a new feature. As a result, no changes or implementations will be made to address this behavior.

Going forward, the grid will not retain or manage filters automatically when the data source changes at runtime. The rationale behind this decision is that the developer responsible for changing the data source is aware of the configuration and structure of the new data. If the new data set differs significantly, it will be up to the developer to handle this scenario appropriately by clearing the filters before or after changing the data source.

We believe this approach ensures greater clarity and control for developers when managing dynamic data in the grid.