[CLOSED] Filter Remotely on Displayed Value

[rbarr]

Hey Guys,

I've got a small problem! I have a grid in which I takes in int values then I use a custom renderers to display what that value means. The problem I have is I'm trying to filter the grid remotely because I use remote paging (I have loads of records and don't want to bring them all down) and I want to allow the users to type in the rendered value not the actual value but I can't get it to work, I get errors because its expecting a int32 and getting a string. I have looked at local filtering with js (which works) but this is no use as it only filters the 20 records which I've pulled into the store.

Thanks Again

[Daniil]

Hi,

Please clarify where exactly are you getting the error? Could you provide a sample to reproduce?

[rbarr]

Hi Daniil,

Thanks for the reply. I'm getting the error in the back end. I can show the code that I used to get it working when using local filtering

here it is

var cnf = function (filter, record) {
    var filterValue = filter.getValue();

    if (filterValue.length == 0) {
        return true;
    }
    var values = filterValue.toLowerCase().split(",");
    for (var i = 0; i < values.length; i++) {
        if (clientNameRenderer(record.data.ClientAccountId).toLowerCase().indexOf(values[i].trim()) != -1) {
            applicationDataGridPanel.getSelectionModel().selectFirstRow();
            return true;
        }
    }
    return false;
}

And the the filter looked like this.

<ext:StringFilter DataIndex="ClientAccountId" >
  <validateRecord handler="return cnf(this, record)" />
</ext:StringFIlter>

This works but I'm trying to do the same but with remote filtering.

Thanks

[Daniil]

Well, yes, you can't use ValidateRecord for remote filtering.

Just to clarify: in remote filtering case GridFilters values are sent to server and you can't get them this way (if you deal with code behind):

string s = e.Parameters[this.GridFilters1.ParamPrefix];

Then you can filter a data as you wish according to these filters values.

In addition, it's not necessary to use the FilterConditions class:

FilterConditions fc = new FilterConditions(s);

if a error happens in that class.

You could extend/override/change that class or just create a new one which would suite your needs.

[rbarr]

Hi Danill,

Thanks for the guidelines, i've now got it working great. So you can mark this as closed.

Thanks again