Custom bool filter and advanced filter questions

$().kendoGrid({
  columns: [
    { 
      field: "FieldName", 
      title: "FieldTitle", 
      template: kendo.template('#= FieldName ? "trueString" : "falseString" #'),
      filterable: { messages: { isTrue: "trueString", isFalse: "falseString" } }
    }
  ]
});

Hi Alexander,

Just wondering if it is now possible to create a custom filter for boolean? If not, is there a different way to filter nullable booleans? The filter currently defaults to the "is true / is false", but no option for neither (null).

Thanks,
Stefan.

Awesome, looking forward to it!

Thanks.

• http://docs.telerik.com/KENDO-UI/api/javascript/ui/grid#configuration-filterable.operators.string.isnull
• http://docs.telerik.com/KENDO-UI/api/javascript/ui/grid#configuration-filterable.operators.string.isnotnull
• http://docs.telerik.com/KENDO-UI/api/javascript/ui/grid#configuration-filterable.operators.string.isempty
• http://docs.telerik.com/KENDO-UI/api/javascript/ui/grid#configuration-filterable.operators.string.isnotempty
• //etc.

Hi Alexander,

My comment was in regard to your response on Feb 7 2013:

I'm trying to setup a custom filter for boolean. Is it possible?
This is not possible - by design boolean fields does not support filter customization

When creating a custom filter, you would be utilizing the UI property of the column's filterable setting, as documented here:
http://docs.telerik.com/KENDO-UI/api/javascript/ui/grid#configuration-columns.filterable.ui

That documentation makes no mention of the fact that creating a custom filter for a Boolean column is not possible.
When you attempt to do so, it simply does not work.  
There is no error, it simply does not work.

That's why I think it would be helpful if the documentation of the UI property mentioned this.

Hello Skip,

Thank you for your feedback, indeed we will update the article. 

Hello.

Can you combine the "isempty" and the "isnull" filter in a way that offers just 1 filter to the user in the grid header? As a user, I do not want to set up 2 filters linked with OR to simply list all entries, that LOOK empty, which can be undefined, null or an empty string. We need a filter like "looksempty" which performs both, the "isempty" and the "isnull" filtering...

Explanation: Some database null-values are not transmitted with JSON, so they are undefined in the datasource. With a template we display them as an empty string, but this does not affect the filtering, which is performed on the datasource. Filtering those undefined values cannot be performed with "isempty". But filtering empty strings cannot be performed with the "isnull" filter...

In .Net there is something like String.IsNullOrEmpty(), which is great. Something like that would be needed in the filtering here as well.

Hello,

I am afraid  that adding a custom filter to the Grid's filter menu is currently not supported If you consider that it would be a useful addition to Kendo UI you could post it as a suggestion in our Kendo User Voice portal. If it gets popular among the community we will consider to implement it in future releases of Kendo UI.

Regarding the current scenario, since a custom client side filtering is required, I would suggest you to implement it outside of the Grid and manually filter the dataSource data with the filter method. This approach allows to set a filter expression containing both operators with "OR" logic. 

Regards,

Telerik by Progress

In the original Admin response it is indicated that 'Checked binding works with check boxes/radio buttons only'.

Does this mean there is a way to change a bool filter from two Radio Buttons to one Checkbox?

Hello Chris,

Indeed the checked binding works only with checkbox and radio buttons. More information can be found in the  Checked Binding article. 

The problem is that boolean columns do not allow any customization ( columns.filterable.ui will do nothing for boolean columns). 

hiii,

am created a published filed(boolean)for this field filterable property is not working according to page wise ...if i filter on 2nd page it is giving me everytime on first page results only using kendogrid .can anyone help me out from this...

       Thank you.

Hello venky,

I am afraid that the provided information is insufficient to be able to determine what is causing the described behavior. It will be great if you can send us a sample dojo example that replicates the problem you are facing. 

Ya sure,

  Server filtering is not working ..here is my code

<div id="orderitems-grid"></div>
    <script>

 $("#orderitems-grid").kendoGrid({
        dataSource: {
            type: "json",
            transport: {
                read: {
                    url: "@Html.Raw(Url.Action("OrderItemsList", "Seller"))",
                    type: "POST",
                    dataType: "json"
                },
                update: {
                    url: "@Html.Raw(Url.Action("UpdateOrderItem", "Seller"))",
                    type: "POST",
                    dataType: "json"
                }
            },
            schema: {
                data: "Data",
                total: "Total",
                errors: "Errors",
                model: {
                    id:"Id",
                    fields: {
                        ProductName: { editable: false,type:"string"},
                        AttributesXml:{ editable:false },
                        SubOrderNumber: { editable: false, type: "number"},
                        PriceInclTax: {editable: false},
                        UnitPriceInclTax: {editable: false},
                        Quantity: {editable: false},
                        SubTotalInclTaxValue: {editable: false},
                        DiscountAmountInclTax: { editable: false },
                        SellerName: { editable: false},
                        OrderItemStatusId: { editable: true },
                        SellerRegisteredCompanyName: { editable: false,type:"string" }
                    }
                }
            },
            requestEnd: function (e) {
                if (e.type == "create" || e.type == "update") {
                    this.read();
                }
                if(e.type=="update" && e.response!="")
                {
                    alert(e.response);
                }
            },
            error: function (e) {
                display_kendoui_grid_error(e);
                // Cancel the changes
                this.cancelChanges();
            },
            pageSize: 25,
            serverPaging: true,
            serverFiltering: true,
            serverSorting: true
        },
        pageable: {
            refresh: true,
            pageSizes: [50, 100, 150, 200],
            buttonCount: 10
        },
        sortable: true,
        resizable: true,
        editable: {
            confirmation: false,
            mode: "inline"
        },
        filterable: {
            extra: false,
            operators: {
                string: {
                    contains: "Contains",
                    eq: "Is equal to",
                    startswith: "Starts with"
                }
            }
        },
        scrollable: false,
        columns: [{
            field: "ProductName",
            title: "Product Name",
            template: '<a href ="@Url.Content("~/Product/Edit/#=ProductId#")">#=ProductName#</a>',
            width: 300
        }, {
            field: "AttributesXml",
            title: "Attributes",
            encoded: false,
            filterable: false,
            width: 150
        }, {
            field: "SubOrderNumber",
            title: "SubOrder No",
            width: 115,
            template: "<a href=\"\" onclick=\"window.open('/Order/GetOrderItemNotes/#=Id#','WindowOrderItemNote','align=center'); return false;\">#=SubOrderNumber#</a>",
        }, {
            field: "UnitPriceInclTax",
            title: "UnitPrice Incl Tax",
            width: 110,
            filterable: false,
            template: '<span style="font-weight:bold;color:\\#0000CD">₹&nbsp;#:UnitPriceInclTax #</span>'
        }, {
            field: "Quantity",
            title: "Qty",
            width: 75,
            filterable: false,
        }, {
            field: "SubTotalInclTaxValue",
            title: "Sub Total",
            width: 100,
            filterable: false,
            template: '<span style="font-weight:bold;color:\\#0000CD">₹&nbsp;#:SubTotalInclTaxValue #</span>'
        },{
            field: "DiscountAmountInclTax",
            title: "Discount",
            width: 100,
            filterable: false,
            template: '<span style="font-weight:bold;color:\\#0000CD">₹&nbsp;#:DiscountAmountInclTax #</span>'
        },{
            field: "PriceInclTax",
            title: "Price Incl Tax",
            width: 110,
            filterable: false,
            template: '<span style="font-weight:bold;color:\\#0000CD">₹&nbsp;#:PriceInclTax #</span>'
        }, {
            field: "SellerRegisteredCompanyName",
            title: "Company Name",
            template: '<a href="Edit/#=SellerId#">#=SellerRegisteredCompanyName#</a>',
            width: 200
        }, {
            field: "OrderItemStatusId",
            title: "Status",
            editor: OrderItemStatusDropDownEditor,
            template: "#=OrderItemStatus#",
            filterable: false,
            width: 250
        }, {
            command: ["edit"],
            title: "Action",
            filterable: false,
            width: 100
        }],

});

</script>

is there anything i missed ??

Hello venky,

According to our documentation for the type of the Kendo UI DataSource the supported values are: 

    - "odata" which supports the OData v.2 protocol
    - "odata-v4" which partially supports odata version 4
    - "signalr"

The purpose of the Kendo UI DataSource type property is to use a predefined transport and/or schema.

I guess that currently the service does not parse the incoming data (filter expression and so on) so the actual filtering on the server is not performed. In the following https://github.com/telerik/kendo-examples-asp-net you can find examples for communication between Kendo UI Grid and web api, services and etc. 

Regards,

Progress Telerik