Hello, a solution to the problem is urgent. Our customers (including several DAX corporations) are extremely dissatisfied. They need a solution. See also: https://www.telerik.com/account/support-center/view-ticket/1557520
Who is the responsible decision maker to ensure that the problem is treated with priority?
Best regards Stefan Aust
Posted on:13 Dec 2022 15:49
The status of the item is indeed "Unplanned" - this indicates the request is valid and will be worked on in a future version of the product but it is not yet scheduled for implementation. Unfortunately, at this stage, I am not able to provide a firm estimate on when it will be included in the product. The best way to follow its progress is to subscribe for the item.
For the time being, an option that I can suggest for optimizing the performance of the TreeView is to load the child items on demand only when the user expands the parent node. You may check the Lazy Loading demo to explore the configuration.
Take your time to revise it and please let me know if any questions appear.
this is unplanned now for over 1 year - is there any chance this ever gets implemented? I think this is a crucial one (same goes for TreeList row virtualization) - as there is no workaround possible (e.g. when the user expands a lot of nodes).
Otherwise, we'll have to look for an alternative.
Posted on:22 Sep 2021 07:48
Thank you for your feedback!
We do have an opened feature request for row virtualization in the TreeList that you may find here - Support for row virtualization. I see you already voted for it and you might also follow it to keep in track with its progress.
I would just like to add: this would also be a useful feature for the TreeList (the row virtualization is missing - column virtualization is already implemented) component as well, which shouldn't be much more work after the TreeView virtualization is implemented.
I think this would also keep your component-features more "consistent"
Posted on:20 Sep 2021 15:06
Indeed, once this feature is available you can use it to improve the overall performance of the TreeList and not only initially. The best way to keep in track with its progress is to follow it.
Once we know which release will contain its implementation, we will update its status in the feedback portal and you will be notified via email accordingly.
I have ticket 1531271 open on this as well. We've had to use some delicate logic to dynamically load every tree branch as it first expands. This can improve performance initially, but as our customers expand more branches, hundreds of nodes can accumulate and performance degrades significantly. We are very keen for this feature.
Posted on:09 Sep 2021 15:18
It will be very helpful
Posted on:09 Sep 2021 15:18
we need this feature as soon as possible, please we need to work!!!!