Telerik Reporting will introduce a GenAI-powered assistant in the Web Report Designer (WRD) to simplify the creation of data presentation items. This feature will allow users to describe their reporting needs in natural language and instantly generate styled, data-bound visualizations. Each proposed report change will be approved or rejected by the user, providing complete control over the result. The initial release will focus on Graph and Gauge items, powered by a set of Design-Time Tools that manipulate the report model and trigger commands in the design-time environment. Future expansions will be guided by the user feedback we collect.

We’re extending the HtmlTextBox to support the <img> tag, enabling inline image rendering within HTML-formatted content. This allows report authors to embed static or data-driven images directly into rich text blocks, improving layout flexibility and reducing the need for separate image elements. The feature will support common attributes and styling, and will render consistently across all supported output formats.

Telerik Reporting will introduce Unicode Bidirectional (BiDi) text layout support in its Skia-based rendering engine. This enhancement will ensure correct visual ordering of mixed RTL and LTR text in reports, improving readability and accessibility for multilingual audiences. The feature will be available across all major rendering formats and platforms.

We will improve the resources serialization when serving reports to be consumed from the report viewer controls. The new serialization will utilize the built-into .NET functionality instead of relying on other libraries. This would improve performance and simplify the deployment process.

We are introducing a dedicated Entity Framework Core Data Source for Telerik Reporting. This component will allow direct binding to DbContext, and provide design-time configuration in SRD for .NET. Expect lifecycle management for DbContext, live data previews, parameterized queries, and compatibility with .NET 8+. Shared Data Sources (SDS) will also be supported for reuse across multiple reports.

We are adding a PrintOnEveryPage property to Table groups in Telerik Reporting. This will allow report authors to repeat group headers across pages for granular control and better readability and compliance with reporting standards.

The implementation of Telerik Reporting REST service based on the ServiceStack framework will be deprecated in the next major release (2025 Q4). Telerik Reporting 2025 Q3 is the last version to include the assemblies and NuGet packages containing the ServiceStack implementation.

After introducing Raw Data export feature to the desktop designers and WInForms report viewer we will introduce this functionality to the Web Report Designer, all Web report viewers, including the native Angular and Blazor components. The feature enhances working with data while designing and previewing reports. Report authors will access unified raw data export during design time through the data source wizards and on demand. When previewing the report document, the end-user will have access to the plain data behind each data item like Table, Chart, or the Report itself for export.

We will introduce lazy loading for large database schemas in the Query Builder tool to improve performance and usability. This enhancement will significantly reduce initial load times and system resource usage when working with complex schemas. When lazy loading is active, the search experience will adapt to focus on expanded nodes, enabling efficient schema exploration.

We will introduce AI-powered sample data generation to simplify the report design process. Report authors will quickly create inline CSV data sources out of another data source definition, providing example data, or using natural language prompts (e.g., "Generate sample data with columns: First Name, Last Name, City"). This feature will make it easier for users to design reports faster, experiment with layouts, and bring their ideas to life with minimal setup effort.

We will implement dedicated data source components to pull data from some of the most popular databases that can currently be utilized using the SQL Data Source component. This will allow easier setup for the report author making them more productive. The considered target data management systems include PostgreSQL, SQLite, MongoDB.

On top of our Skia-based report generation engine implementation, we will compile a WebAssembly containing this engine. Effectively, web apps will be able to generate reports directly on the client.

We will expose the available settings to each export format to the end-user so that they have granular control over the produced document.

We will extend the available out-of-the-box functions that can be utilized when composing expressions. Additionally, we will make it easier to extend the available functions.

We will make it possible to present data that is joined from more than one data source. This will bring more flexibility into the hands of the report author. Imagine joining data from a web service providing instant stock rates with the client accounts' holdings for example. No warehouse in the middle of the process. No delay.