New to Telerik UI for Blazor? Download free 30-day trial

Blazor TreeList Filtering Overview

The TreeList component offers built-in support for filtering.


To enable filtering, set the FilterMode property of the treelist to one of the following values:

The behavior of the filter input and the available filter operators will depend on the column data type. For example, a boolean field will only have the options "is true" and "is false" and will not have operators like "contains" or "greater than".

You can filter more than one column at a time, and all filter rules will be applied together with an AND logic.

You can prevent the user from filtering a certain field by setting Filterable="false" on its column.

Filtering keeps an item's parent(s) in the list, so you may see item that do not match the criteria. This is required so you can actually navigate to and see the items that match.

Filtering keeps the expanded/collapsed state of items. For example, if filtering leaves a child whose parent is collapsed, you will only see the collapsed parent.

More Filtering Options

In addition to the two main filtering modes, the treelist offers two more features that can enhance the user experience when looking for data:

  • A searchbox in the toolbar can amend the filters and let the user look up many fields at once

  • The filter menu can show a list of checkboxes with the distinct values from the data to make filtering resemble Excel.

  • You can customize the appearance and behavior of the filters through the filter templates.

Filter Descriptors

The TreeList filter state is stored in CompositeFilterDescriptors. The below information is important if you want to get or change the TreeList filters programmatically.

Each CompositeFilterDescriptor contains a collection of FilterDescriptors. All descriptors in the collection are applied with an AND or an OR LogicalOperator.

  • Filter Row - each CompositeFilterDescriptor targets a specific field. By default, one filter can be applied to a field using the Filter Row operator. The filter value is stored in the first FilterDescriptor instance of the CompositeFilterDescriptor for that field.

  • Filter Menu - each CompositeFilterDescriptor targets a specific field. Filter values from the separate filter operators in the menu are stored in different FilterDescriptor instances of the dedicated CompositeFilterDescriptor for that field.

  • SearchBox - one CompositeFilterDescriptor is created in the state when the user types in the Searchbox. By default, it targets all string fields. A dedicated FilterDescriptor instance is added to this CompositeFilterDescriptor for each string field. Each FilterDescriptor instance contains the filter value typed in the Searchbox.

Customize The Filter Editors

You can customize the filter editors declaratively for some data types. It is possible to change the editor component or the editor format.

TreeListColumn Parameter Type Works for Description
FilterEditorType TreeListFilterEditorType enum DateTime columns The component, which the TreeList will render for filtering (DatePicker or DateTimePicker).
FilterEditorFormat string DateTime and numeric columns The Format of the filtering component. Do not use a placeholder (e.g. set "D", not "{0:D}").
@* Using FilterEditorType and FilterEditorFormat parameters *@

<TelerikTreeList Data="@Data" 
                 IdField="Id" ParentIdField="ParentId" 
        <TreeListColumn Field="Name" Expandable="true" Width="320px"></TreeListColumn>
        <TreeListColumn Field="Id"></TreeListColumn>
        <TreeListColumn Field="@(nameof(Employee.HireDate))"
                        FilterEditorFormat="yyyy-MM-dd HH:mm"
                        Title="Hire Date">

@code {
    public List<Employee> Data { get; set; }

    protected override async Task OnInitializedAsync()
        Data = await GetTreeListData();

    public class Employee
        public int Id { get; set; }
        public int? ParentId { get; set; }
        public string Name { get; set; }
        public DateTime HireDate { get; set; }

    async Task<List<Employee>> GetTreeListData()
        List<Employee> data = new List<Employee>();

        for (int i = 1; i < 15; i++)
            data.Add(new Employee
                Id = i,
                ParentId = null,
                Name = $"root: {i}",
                HireDate = DateTime.Today.AddYears(-i)

            for (int j = 2; j < 5; j++)
                int currId = i * 100 + j;
                data.Add(new Employee
                    Id = currId,
                    ParentId = i,
                    Name = $"first level child of {i}",
                    HireDate = DateTime.Today.AddYears(-j)

                for (int k = 3; k < 5; k++)
                    data.Add(new Employee
                        Id = currId * 1000 + k,
                        ParentId = currId,
                        Name = $"second level child {k} of {i} and {currId}",
                        HireDate = DateTime.Today.AddYears(-k)
                    }); ;

        return await Task.FromResult(data);


  • The treelist uses Activator.CreateInstance<TItem>(); to get the type of the item it is bound to in order to generate proper filters and filter operators for them. Thus, the Model should have a Parameterless constructor defined.

See Also

In this article