Multiple filters on same field not working

[Martin]

Filtering a kendo dataSource connected to everlive doesn't seem to work if you have a two filters on the same field/column like this:

[
   {field: "State", operator: "neq", value:"active"},
   {field: "State", operator: "neq", value:"new"}
]

This gets translated to an everlive filter that looks like this: X-Everlive-Filter:{"State":{"$ne":"new"}}

Seems like the first filter gets ignored. Using multiple filters on different fields works though.

Doing this on a normal kendo datasource (not everlive) works fine.

Am I doing something wrong or is this a bug?

[Anton Dobrev]

Hello Martin,

Thank you for reporting this. I can confirm that this is a bug in the "Everlive" dialect of the Kendo UI Data Source that will be addressed.

I updated your Telerik Points as a token of gratitude for your valuable input.

Let me know should you have any further questions or suggestions.

Regards,
Anton Dobrev
Telerik

 

 

[Martin]

Any news for this bug? Do you know when it will be fixed?

[Anton Dobrev]

Hi Martin,

Thank you for getting back to us.

The bug is logged in our issue tracking system and will be addressed. However, at the current stage we cannot commit to a particular time-frame for the fix.

As a workaround I can suggest that you pass the filter to the transport.read.beforeSend configuration of the data source. Actually this is the configuration setting of the underlying AJAX request executed by jQuery.

You can also modify the request before creating, updating or deleting items.

For example:

var filterExpression = {
    "$and": [{
        "field1": {
            "$ne": "active"
        }
    }, {
        "field1": {
            "$ne": "new"
        }
    }]
};

var dataSource = new kendo.data.DataSource({
    type: 'everlive',
    transport: {
        typeName: 'Activities',
        read: {
            beforeSend: function(xhr) {
                xhr.setRequestHeader('X-Everlive-Filter', JSON.stringify(filterExpression));
            }
        }
    },
    schema: {
        model: {
            id: Everlive.idField
        }
    }
});

Thus you will be able to use a multiple filter on the same field.

I hope that this will be helpful for you.

Regards,
Anton Dobrev
Telerik

 

 

[Calin]

Hello Anton, 

I have just tried te solution but I get that setRequestHeader is undefined. Any thoughts?

Thanks,

CalinC

[Calin]

fyi, I'm trying it into a hybrid mobile app.

[Anton Dobrev]

@all

This bug was fixed in previous releases of the JavaScript SDK.

@Calin

If you need to set a custom filter via the header (like a GeoPoint filter) see the headers option for custom filtering (instead of setRequestHeader) as shown here.

Please note that the headers will be set only at the time of initializing the data source (as for the current design) but you can also modify the filtering header dynamically (if needed) via the beforeExecute event.

I hope this helps.

Regards,
Anton Dobrev
Telerik by Progress