What was the issue with rc-tree?
The previous tree renderer was based on the stable but performance-intensive rc-tree library when dealing with deep or large data structures.
Typical symptoms:
- Long loading times when initializing the designer
- Noticeable stuttering when navigating or performing drag & drop
Especially in the Web Report Designer, which is supposed to be performant, flexible, and responsive, that’s obviously counterproductive.
What’s different now?
With version 31, the entire tree renderer was migrated internally: instead of rc-tree, the new react-arborist library is now used – a powerful tree component optimized for large .NET data models.
The best part: the migration only affects the technical foundation. The interface, API, and user behavior remain exactly the same.
What does this mean for you as a developer?
- Faster startup: Even large data sources load noticeably quicker.
- Smoother drag & drop: Even with deeply nested structures, the Web Report Designer remains performant.
- Clearer debugging: Performance issues are easier to isolate since the tree is no longer the bottleneck.
Questions you might have
Do I need to adjust my integration?
No, the interface, API, and user behavior remain unchanged. There’s no migration effort.
Are there visual differences?
No. Drag & drop, context menus, and appearance stay exactly the same.
How much faster is the new DataTree really?
Internal benchmarks show 50–70% faster loading times with large data sources.
The new DataTree is therefore a classic under-the-hood optimization.
Especially if you work with large data sources in the Web Report Designer, the new DataTree will significantly speed up your workflow.
Benjamin works as a full stack developer at combit. In addition to being a part of the dev team, he is also involved in vocational training. In his free time, he engages for the volunteer fire department.
