3.0 provide a single filter for the entire grid

[qorsmond]

Wow first off thanks for this awesome data grid! Loving the new features.

I have a use case where the ui is primarily driven by one search box external to the grid, where I used to use the filterOptions to set up the filters.

As far as I can tell that is no longer available as the filtering is only available on the columns in the grid.

Is there any way to get the filters to work with an external input? I came across the rowSearcher service but I am not sure how to hook it up in the controller.

Any guidance will be much appreciated.

[andresLopera]

you should see this case #1262

[PaulL1]

@andresLopera: that issue relates to filters in the sense of internationalisation. I think this question relates to filters in the sense of "please free text search across all the data in my grid".

I think that the changes would be in rowSearcher, and maybe a few ancillary places. You'd introduce some sort of "globalSearch" parameter, perhaps in gridOptions, to which a user could bind. And everywhere in rowSearcher that decides whether a row matches or not, you'd add some sort of conditional that says || row.matches(gridOptions.globalSearch).

Presumably any data that wasn't string would first need to be cast to a string to search over it. The first time contributing guide (https://github.com/angular-ui/ng-grid/blob/master/CONTRIBUTING.md) would be a good starting point.

[Hoakie]

If I understand the OP, they may be looking for something implemented like this: http://plnkr.co/edit/cTxLLI84kXy9HR2JekbX?p=preview

This example uses straight angular filtering functionality in the controller based on input and updates the grid's data. I provided three grids to demonstrate. The first two grids demonstrate filtering across whole data set and does not consider what columns are in defined in the grid at all.

To demonstrate this, type the letter T in the search box, notice that the row for Cox Carney remains in the filtered result set because the t in true for employed (even though it is not displayed in the second grid). Although it works, I would think it would be a confusing use case since you can not visualize why the record is returned in the middle grid.

The third grid makes use of a custom filter. This filter takes the data, the grid and the query term and only returns items that match fields defined in columnDefs. now if you look at grid3 with you type 't', you will notice no records match since the Employed column is not defined.

I think the later is most similar to what PaulL1 envisions for his enhancement implementation. I know my solution doesn't make use of ui-grid built in functionality, but may provide a work around until it the enhancement is released.

[KreepN]

Plnkr - Multi-column global grid search

Based it off of Hoakie's demo. Useful for others wanting something temporary until something more permanent is added to the grid itself.

Try searching for "Waters".

[aborchew]

@Hoakie 's solution was massively helpful for me. For my use case, we wanted out users to be able to search for rendered content - not necessarily the actual data that was being returned. Specifically, data that was being manipulated by a cellFilter parameter in a column config. Based on the mentioned solution, I created this plnkr. Notice how the last grid has a cellFilter converting years to months and appending a string to the end of the value. You can now search for something like 480 months and notice that, although there is no data in the model with that string, it will match the rendered content correctly.

Hopefully it's useful someone!

This might be related to #2796. Can we have a 'filter' label please?

[marc-rutkowski]

My own enhancement of @aborchew and @Hoakie solution to avoid error when using cellFilter with parameters (i.e. " date: 'yyyy' ")

Plnkr