The aggregates field is currently available only for kendoTreeListFooterTemplate:
https://www.telerik.com/kendo-angular-ui/components/treelist/aggregates/#toc-aggregating-flat-data
But in some scenarios, the aggregates need to be displayed inside the headers as well. Please provide the aggregates field in the kendoGridCellTemplate.
So far the only approach where this can be achieved is to use manual aggregation and some custom code:
<ng-template kendoTreeListCellTemplate let-dataItem>
{{dataItem.name}} - <strong> {{ data.aggregates.name.count }} employee(s)</strong>
</ng-template>
Provide a built-in functionality for the TreeList that would allow binding the component to data with the following structure:
const data = [
{ path: ['node1', 'node2'], property1: value, property2: value },
{ path: ['node1', 'node2', 'node3'], property1: value, property2: value },
];
The structure provides particular paths for the leaf nodes (last children) that determine the hierarchy within the component and additional fields that correspond to the columns' definition of the component.
We would like to provide the same loading behaviour to our customers by displaying a custom loading spinner.
Therefore I request the feature for a "Angular TreeList Loading Template", like it is already available for kendoGrid.
Provide the ability to customize the drag hint for the row reordering of the TreeList similarly to the available Grid feature:
The drag selection is enabled immediately after dragging the cursor a little (1-2px). This causes issues when a row is expanded/collapsed first then clicking the checkbox as sometimes, the cursor is dragged in the checkbox. Then drag selection resets the previously selected rows. Here is a screencast of the issue:
https://screenrec.com/share/y6pPGWjUZH
- Expand a row
- Click and drag the cursor in the checkbox (1-2px)
https://stackblitz.com/edit/angular-qnaphv-2nszye
The drag selection should not be enabled.
The Grid has a logic for enabling the drag selection after N-pixels of dragging. Could be reused in TreeList as well.
Hi,
We've noticed a significant difference in how the "Select All" checkbox functions in the Grid and TreeList when paging is enabled.
Our application uses both components, and users expect them to behave consistently. However, we’ve identified several issues:
1. Inconsistent User Expectations
In the Grid, "Select All" applies only to the current page.
In the TreeList, "Select All" applies to all pages, including hidden rows.
This inconsistency can confuse users who switch between these components, leading to unexpected behavior and frustration.
2. Confusing Bulk Actions
In the Grid, users understand that selections are limited to the visible page.
In the TreeList, users might unknowingly select thousands of records, potentially causing unintended bulk updates or performance issues.
3. Risk of Data Loss or Errors
Users assuming the TreeList behaves like the Grid might:
Select all rows, perform an action (e.g., delete or update), and unintentionally affect all pages instead of just the current one.
This can lead to accidental data loss or incorrect modifications.
We need a consistent approach to "Select All" behavior across both components to prevent confusion, errors, and performance issues.
Expected behavior
If "Select All" is checked, it should:
- Select all visible rows on the current page.
- Select all children of selected parents, even if those children are on other pages.
- Maintain selection when navigating to another page.
If it should be submitted as a bug, please let me know.