Unplanned
Last Updated: 20 May 2024 12:30 by Ed
Created by: Ed
Comments: 0
Category: TreeList
Type: Feature Request
1
Missing AdditionalViewData Method for the TreeList
Unplanned
Last Updated: 28 Oct 2021 14:42 by ADMIN
Created by: Rob
Comments: 0
Category: TreeList
Type: Feature Request
1

Exporting large amounts of data is very slow. 8000 records with 25+ columns take approximately 50 seconds to be sent to the export action. Increasing the number of records past 8k slows the export further, to a point where it takes minutes for the data to be sent to the controller.

Exemplary configuration:

@(Html.Kendo().TreeList<MVCTreeListTest.Models.CategoryModel>()
	.Name("treelist")
	.Columns(columns =>
	{
		columns.Add().Field(e => e.Name).Width(200);
		columns.Add().Field(e => e.Description).Width(300);
		columns.Add().Field(e => e.Field1);
		columns.Add().Field(e => e.Field2);
		columns.Add().Field(e => e.Field3);
		columns.Add().Field(e => e.Field4);
		columns.Add().Field(e => e.Field5);
		columns.Add().Field(e => e.Field6);
		columns.Add().Field(e => e.Field7);
		columns.Add().Field(e => e.Field8);
		columns.Add().Field(e => e.Field9);
		columns.Add().Field(e => e.Field10);
		columns.Add().Field(e => e.Field11);
		columns.Add().Field(e => e.Field12);
		columns.Add().Field(e => e.Field13);
		columns.Add().Field(e => e.Field14);
		columns.Add().Field(e => e.Field15);
		columns.Add().Field(e => e.Field16);
		columns.Add().Field(e => e.Field17);
		columns.Add().Field(e => e.Field18);
		columns.Add().Field(e => e.Field19);
		columns.Add().Field(e => e.Field20);
		columns.Add().Field(e => e.Field21);
		columns.Add().Field(e => e.Field22);
		columns.Add().Field(e => e.Field23);
	})
	.Toolbar(tools => tools.Excel())
	.Filterable(filterable => filterable
	.Extra(false))
	.Excel(excel => excel
		.FileName("Test.xlsx")
		.Filterable(true)
		.AllPages(true)
		.ForceProxy(true)
		.ProxyURL(Url.Action("Export", "Home"))
	)
	.Sortable()
	.DataSource(dataSource => dataSource
		.PageSize(250)
		.ServerOperation(false)
		.Read(read => read.Action("GetItemCategories", "Home"))
		.Model(m =>
		{
			m.Id(f => f.Id);
			m.ParentId(f => f.ParentCategoryId);
			m.Expanded(true);
			m.Field(f => f.Name);
			m.Field(f => f.Description);
			m.Field(f => f.IsActive);
		})
	)
	.Height(600)
)

Unplanned
Last Updated: 11 Jun 2021 06:45 by ADMIN
Created by: Uffe
Comments: 0
Category: TreeList
Type: Feature Request
5
Make both TreeList functionalities (rowTemplate and inline editing) work together.
Unplanned
Last Updated: 07 Apr 2021 22:42 by ADMIN
Created by: Rob
Comments: 0
Category: TreeList
Type: Feature Request
1

Hi Team, 

I would like to request the ability to editing with batch editing for boolean fields where the template could utilize a checkbox similar to this example.

Thank you!

Unplanned
Last Updated: 06 Apr 2021 06:01 by ADMIN
Created by: Cerealog Dev
Comments: 1
Category: TreeList
Type: Feature Request
0

It would be great if the TreeList could have the same LoadSettings method than the grid widget.

We could easily load user preference.

 

Unplanned
Last Updated: 18 Nov 2020 10:54 by ADMIN
Created by: Martin
Comments: 0
Category: TreeList
Type: Bug Report
0

Bug report

HTML-encoding (columns.encoded) does not work in treeList with InCell editing enabled.

Reproduction of the problem

Refer to below Dojo:

https://dojo.telerik.com/EmEKukiD

Expected/desired behavior

When columns.encoded is set to true value shall be HTML-encoded

Environment
Kendo UI version: [all]
Browser: [all]

Unplanned
Last Updated: 06 Apr 2020 07:57 by ADMIN
Created by: Martin
Comments: 1
Category: TreeList
Type: Feature Request
0

In a Grid, you can include aggregates from other columns in a footer template. Please add this feature to TreeList.

Also, other useful features would be:

1. Enable or hide footers for expanded nodes. Currently, if there are any footer templates defined, then a footer row is rendered for each expanded node. Please can we have some control over which of these footer rows are rendered. For example, having them rendered only at the top level.

2. Provide some means of controlling whether or not to include child rows' values in the aggregates.

For example, I currently have a TreeList where some values are already the totalled across any child rows - this totalisation is done by our business layer. However, we want to include a Grand total in the footer, This Grand Total needs to be the total values summed on the top-level rows ONLY and not their children. I am having to write custom code to do this.