TreeList

The Telerik UI for Blazor TreeList component is a data container element, similar in many ways to the Grid. Unlike the Grid, it stores and displays a list of items in a hierarchy. It is designed to be used for when you want to combine the clean and accessible UI of a Grid but also add a tad of extra information – namely some relationship between the items in the list. Examples include:

• Listing all employees of the same organizational hierarchy – each of them has a name, title, location, salary, etc. but you can conveniently show the managers by having their rows contain their team’s members.
• Listing all locations of a large brand – locations might be grouped by their country of origin

Let your users find the data they are looking for with the TreeList Search Box. Enabling this feature adds a text box in which text can be typed and the TreeList will filter out records which do not match the text.

Use the TreeList column Visible property to programmatically control which Grid columns are visible. When a column needs to stay hidden at all times, you can directly set the column property Visible to false. However, you can also dynamically manage the column’s visibility in other cases when you need to provide conditional visibility (e.g. to hide currently uninteresting data).

By default, the TreeList only allows a single criteria to be used when sorting. When this option is enabled, users can choose to do better—sorting on a column and then sorting another one applies both sorting criteria to the data (in the order specified).

Providing the data for the TreeList component can be done either by:

• a tree-like structure which contains all nested items as children of the parent item (e.g. your Employee class would have a Children array) OR
• passing a flat list of all the items that need to be displayed and marking the items that need to be nested with additional identifiers (e.g. your Employee class would have a ParentId)

Data binding the entire list data makes usage trivial and allows you to focus on other more important things – like if you want your data to be loaded on demand which we also support.

Making good use of this component requires it to be very flexible to be useful in all situations. For this reason, the columns of the Telerik UI for Blazor TreeList can be

• reordered and resized
• frozen so they always stay in sight
• -virtualized so the component doesn’t render columns which are not currently visible on screen
• generated automatically from your model so you don’t even have to specify them
• can show commands instead of data (e.g. buttons to initiate editing, submitting or other operations on the data)

The TreeList implements dedicated CRUD events to make editing easy. The full list of events is too large to be listed but suffice it to say we have everything covered in the docs. There are 3 distinct editing modes:

• Inline editing lets the user directly modify any given entry and all of

  its columns. This editing mode is a good mix between being fast to access and letting the user change everything.
• PopUp editing has the component display a pop up with all values of the current entry displayed like a form. This is editing mode provides users with the most control and visibility over what’s being changed and supports validation.
• InCell editing lets the user click the cell and immediately type the new value. This is the simplest editing mode for users.

The TreeList also provides a toolbar to which you can add actions not tied to a given row. There is one built-in command – Add. Custom commands can be added declaratively – you only need to specify name, an optional icon and a function to be called when the corresponding button is pressed.

The Telerik UI for Blazor TreeList control works with templates to let you override the visuals of all of its components – from the looks of cells, columns and rows, to column headers, and even specifying custom editors for edit mode or custom UI for filtering!

The Telerik UI for Blazor TreeList’s OnCellRender event is triggered whenever a TreeList columns is rendered. Called for every cell in the column, the event handler receives data about the items for which the given cell is used. This is the best place to modify the CSS class of the cell depending on some condition in the data.

The OnRowRender event is triggered when some row of the Grid is rendered. It is called once for each item in the collection. The item itself is passed to the event handler. This method is to be used to conditionally format the different rows (e.g. put a background on every row containing a certain substring in one of its columns).

By default, the data in the TreeList is not selectable but you can change it to allow either single-row or multi-row selection. Selection works as you expect it - use Ctrl or Shift to extend or reduce the selection. Selected rows are accessible programmatically through a property so that you can execute commands only on them. With multiple selection, you can also have the Treelist select children of selected rows automatically.

Large data sets are hard to read and understand without some structure. That’s why facilities like paging are crucial for users to make sense of the patterns and hidden information the list contains.

The third pillar of user interactions for large amounts of data is sorting. Similarly to filtering, the UI interactions for sorting are built in the component – clicking on a column’s header will sort all entries depending on the values in it. Sorting can be optionally disabled on columns for which it doesn’t make sense.

Filtering is another key feature for users to understand the structure in the data. Filtering is supported on any column in the TreeList and comes out of the box. The component will check the type of the data in the column in order to make a decision on what type of filtering is required. For example, if the values are numbers, the filter will suggest predicates like “Is Equal To” or “Is Greater Than”.

Two modes of filtering UI are supported:

• Filter Row displays the filtering options in between the column headers and the column values.
• Filter Menu adds a button on each column. When clicked, that button displays many filtering options for the current column.

Filter row is easier and faster to use whereas Filter Menu has more powerful options. It’s up to you to decide which one should the user be presented with.

The TreeList presents end-users with many configurable elements – e.g. the currently applied filtering and sorting rules. The set of configurable elements is the TreeList’s state. The component allows developers to programmatically save, load and change the current state. This means you can make sure the end-user always starts from the same place they were at the last time they used your application.

The TreeList fires a variety of events to notify programmers for when an action should be taken. These includes data management events like OnCreate, OnUpdate and OnDelete, visibility events like OnExpand and OnCollapse and others. The full list and information about the condition under which they are triggered is available in our documentation.