When filtering the data, Is there a way to use different TextMatchStyle for the different fields?
Here is the use case:
- If I have a listGrid
- When I create it, I set some criteria by executing ListGrid.fetchData(criteria). When I do this, the text match style will be exact, exactly what I want, and the wanted records are displayd.
- Later, the user types in something into the filter row (for an other field), to narrow down the search. This causes an autoFetch to happen, with text match style set to subString.
- Since the text match style is now substring, there are new matches, which the original filter excluded, because are not exact matches
- So, after adding further conditions (by typing into the filter row), the user actually ends up with _more_ records, than before the filtering! (I have just seen this actually happening.)
I guess this is not what anybody wants; adding further conditions should not relax the already configured ones.
It's reasonable to assume substring for the user-filtered fields, but the code-configured criteria should be interpreted as configured.
The solution would be to define different text match styles per field, instead of the current global one.
Do you agree with the above?
Here is the use case:
- If I have a listGrid
- When I create it, I set some criteria by executing ListGrid.fetchData(criteria). When I do this, the text match style will be exact, exactly what I want, and the wanted records are displayd.
- Later, the user types in something into the filter row (for an other field), to narrow down the search. This causes an autoFetch to happen, with text match style set to subString.
- Since the text match style is now substring, there are new matches, which the original filter excluded, because are not exact matches
- So, after adding further conditions (by typing into the filter row), the user actually ends up with _more_ records, than before the filtering! (I have just seen this actually happening.)
I guess this is not what anybody wants; adding further conditions should not relax the already configured ones.
It's reasonable to assume substring for the user-filtered fields, but the code-configured criteria should be interpreted as configured.
The solution would be to define different text match styles per field, instead of the current global one.
Do you agree with the above?
Comment