Hello everyone,

Here are the highlights of the new online resources we published this week from 10 Nov 2025 to 17 Nov 2025:

Article: https://docs.telerik.com/reporting/upgrade/2025/2025-q4-19-3-25-1111
Summary: This upgrade guide explains how to move your projects to Telerik Reporting 2025 Q4 (version 19.3.25.1111), outlining the steps to update project references and NuGet packages and the compatibility requirements for .NET targets, Report Designers, and web/desktop Report Viewers. It lists breaking changes, deprecations, and service/runtime configuration updates so you can adjust code and deployment settings during the upgrade.

Article: https://docs.telerik.com/reporting/ai-coding-assistant/changelog
Summary: Review the Telerik Reporting AI Coding Assistant changelog to track release notes by version, including new features, improvements, and bug fixes. Use it to assess compatibility and plan upgrades for your Telerik Reporting projects.

Article: https://docs.telerik.com/reporting/knowledge-base/changing-data-point-label-position-bar-graph
Summary: This article shows how to control data point label placement in a Telerik Reporting Graph Bar series by setting BarSeries.DataPointLabelStyle.Position (e.g., InsideEnd, OutsideEnd, Top, Bottom, Left, Right). It also demonstrates using an expression on Position to handle positive vs. negative values and vertical vs. horizontal orientation so labels render correctly without overlapping.

Article: https://docs.telerik.com/reporting/designing-reports/report-designer-tools/web-report-designer/configuring-report-templates
Summary: This article shows you how to enable and configure report templates in the Telerik Reporting Web Report Designer by wiring a template source into the Reporting REST service (for example, a file-system folder) and exposing it to the designer. You’ll define template metadata (name, category, description, thumbnail), make templates appear in the Template Gallery, and set a default template used when creating new reports.

Article: https://docs.telerik.com/reporting/knowledge-base/how-to-edit-a-report-template
Summary: This article shows you how to edit a Telerik Reporting report template by opening the template definition (.trdx or .trdp) in the Standalone or Visual Studio Report Designer, updating layout/styles, and saving it to the Designer’s Templates folder so it’s available when you create new reports. It explains how to add a custom template instead of modifying the built-in ones and clarifies that templates affect only newly created reports, not existing definitions. It also covers where the designer looks for templates and how to refresh the template list after changes.

Article: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/web-application/react-report-viewer/how-to-use-with-report-server-net
Summary: You will configure the React Report Viewer to consume reports hosted on Telerik Report Server .NET: set the viewer’s serviceUrl to the Report Server REST endpoint, supply a Report Server report source by path or ID with parameters, and enable CORS. The article covers authentication (cookie or bearer token) and how to attach credentials to viewer requests so your React app can load and render reports from the server.

Article: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/web-application/native-angular-report-viewer/how-to-use-with-report-server-net
Summary: Learn how to connect the Native Angular Report Viewer to Telerik Report Server (.NET) by targeting the server’s Reporting REST service and using a ServerReportSource with a report ID or path (plus parameters). You configure CORS on the server, authenticate via cookies or bearer tokens, and enable the viewer to send credentials so your Angular app can load secured reports from Report Server.

Article: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/web-application/angular-report-viewer/how-to-use-with-report-server-net
Summary: This article shows how to integrate the Telerik Angular Report Viewer with Telerik Report Server (.NET) to render server-hosted reports in an Angular application. You configure the viewer with the Report Server REST endpoint, set up authentication (username/password or bearer token), select a report by ID or path, and pass parameters. It also covers CORS/HTTPS requirements and cross-origin considerations needed for the viewer to communicate with the Report Server.

Article: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/web-application/native-blazor-report-viewer/how-to-use-with-report-server-net
Summary: Learn how to render reports hosted in Telerik Report Server with the Native Blazor Report Viewer by pointing the viewer to the Report Server REST endpoint and using the Report Server report source. You’ll configure the viewer’s service URL, obtain and provide a Report Server auth token, select the report by path or ID, pass parameters, and handle CORS when the app and server are on different hosts.

Article: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/web-application/html5-report-viewer/html5-report-viewer-with-report-server-net
Summary: This article shows how to embed the HTML5 Report Viewer in ASP.NET MVC or WebForms and connect it to Telerik Report Server via its REST API to render server-hosted reports. Configure the viewer’s serviceUrl to the Report Server endpoint, set a server reportSource by report ID or URI, and implement authentication to obtain and attach a bearer token; it also covers passing parameters and handling cross-origin requests. Examples are provided for client-side initialization and MVC/WebForms wrappers.

Feel free to check them out and share your thoughts!

The Telerik Team

---------------------------------------------------------------------------------------------------------------------------------------------------------

Hello everyone,

Here are the highlights of the new online resources we published this week from 29 Oct 2025 to 05 Nov 2025:

Article: https://docs.telerik.com/reporting/interactivity/ai-powered-insights-overview
Summary: AI-powered Insights in Telerik Reporting lets users query and get natural-language summaries of the data currently rendered in a report directly inside the web report viewer. To enable it, configure an LLM provider in your Reporting REST service (OpenAI, Azure OpenAI, or another OpenAI-compatible endpoint), enable the AI Insights UI in the viewer, and optionally customize the system prompt, allowed models, data scope, and token/request limits. You control what report data is sent to the LLM and can restrict PII and usage to meet security and compliance requirements.

Article: https://docs.telerik.com/reporting/interactivity/built-in-client-integration-ai-insights
Summary: Use the AI Insights panel in Telerik Reporting viewers to let users ask questions and generate summaries for the current report via OpenAI or Azure OpenAI, with all LLM requests routed through the Telerik Reporting REST Service. You enable it per viewer (HTML5/MVC/Angular/React/Blazor) and configure the server with the provider, API key, and model/deployment; you can customize prompts, control what report content is sent to the model, and secure access with authentication and CORS.

Article: https://docs.telerik.com/reporting/knowledge-base/combobox-parameter-editor-virtualization
Summary: Learn how to enable virtualization for the ComboBox parameter editor in Telerik Reporting’s HTML5/Web Report Viewer to handle large parameter value lists. You’ll register a custom parameter editor that wraps a Kendo UI ComboBox with virtualization, remote data (server paging/filtering), and a valueMapper so selected values are resolved and preselected correctly. Use this pattern when a report parameter exposes thousands of available values to reduce initial load, memory usage, and network payload.

Article: https://docs.telerik.com/reporting/interactivity/custom-client-integration-ai-insights
Summary: Implement AI insights in Telerik Reporting by adding a custom interactive action to report items and handling it in the HTML5 Report Viewer. You pass the relevant report context (fields/parameters) to the client, call a server endpoint that proxies OpenAI/Azure OpenAI, and render the response in the viewer while keeping API keys and validation on the server.

Article: https://docs.telerik.com/reporting/interactivity/customizing-ai-powered-insights
Summary: Configure AI-powered insights in Telerik Reporting by defining system and user prompt templates, selecting the report/data scope included in the prompt, and wiring providers such as OpenAI or Azure OpenAI with model, temperature, and token settings. The article shows how to enable the feature in the Report Viewer/REST service, restrict and transform the data that leaves your app, and handle request/response events to validate, redact, log, or cancel AI calls.

Article: https://docs.telerik.com/reporting/licensing/license-troubleshoot
Summary: This article helps you troubleshoot Telerik Reporting licensing issues such as trial watermarks, “Invalid license” errors, and CI/build server failures. You’ll verify that your project references commercial (non-trial) assemblies with matching versions, clean bin/obj, and for .NET Framework ensure a valid Embedded Resource license.licx and LC.exe on build agents; for .NET (Core/5+), remove license.licx and rebuild. It also covers upgrades and removing stale GAC or trial assembly references that trigger trial behavior.

Article: https://docs.telerik.com/reporting/knowledge-base/removing-save-as-option-report-designer
Summary: Learn how to remove or disable the Save As command in Telerik Reporting’s Web Report Designer: hide the Save As button in the client configuration and enforce the restriction server-side by rejecting create operations in your custom report storage/service. Use this to prevent users from cloning reports and allow only in-place Save to the existing item.

Article: https://docs.telerik.com/reporting/knowledge-base/rotate-images-picturebox-telerik-reporting
Summary: Learn how to rotate images in a Telerik Reporting PictureBox when rotation isn’t supported natively. You’ll add a C# user function that uses System.Drawing to rotate a byte[]/Image by a given angle, then call it from the PictureBox.Value expression (e.g., with a report parameter for the angle) and adjust Sizing to fit. The article covers handling image formats/transparency and returning the rotated bitmap for all renderers.

Article: https://docs.telerik.com/reporting/embedding-reports/display-reports-in-applications/web-application/html5-report-viewer/using-in-razor-pages-app
Summary: Learn how to add the Telerik Reporting HTML5 Report Viewer to an ASP.NET Core Razor Pages app by hosting the Reporting REST service and wiring up the client viewer. You will install the Telerik.Reporting and Telerik.Reporting.Services.AspNetCore NuGet packages, configure ReportServiceConfiguration and a ReportsController derived from ReportsControllerBase via dependency injection and routing in Program.cs, then include the required jQuery/Kendo and viewer scripts/styles in a .cshtml page and initialize the viewer with a serviceUrl and reportSource. The article also covers resolving reports from a folder (UriReportSourceResolver) and using file-based storage.

Feel free to check them out and share your thoughts!

The Telerik Team

Hello Supports,

I want to try and install Nuget packages Telerik.Reporting.Services.AspNetCore for my Asp.net Core project but it isn't found.

when I go to the option "Manage Nuget packages", these are no available the packages to download (see the attached file).
Is it missing from the private nuget feed ?

Thank You.

Hello Telerik Reporting Community,

We have released a new version of Telerik Reporting today, 2024 Q1 (18.0.24.130). Please update your existing installation at your earliest convenience.

You can review the Legacy Installer Vulnerability - Telerik Reporting article to learn more details about why we are recommending customers to update.

To get the new version, take the following steps:

1. Go to Downloads | Your Account. 
2. Select Telerik Reporting.
3. Download the msi installer file, run it, and follow the steps to completion.

Notes

As the KB article explains, the issue pertained only to the old installer component, and not Telerik Reporting contained within the installation package. It does not affect any applications you’re using Telerik Reporting with.

If you have a rare situation where you cannot update the PC installed version, there are various ways to keep a project using an older version of reporting even though the PC has a newer version installed.

• NuGet Option: Update your projects to use the Telerik Reporting NuGet packages, instead of local DLLs (see https://docs.telerik.com/reporting/getting-started/installation/installation-approaches#using-nuget-packages).

• Copied Assemblies Option: Copy the older version’s DLLs to the project directory, then update the project references to use the copied assemblies (instead of the assemblies in C:/Program files (x86)/Progress/Telerik Reporting [older version]/)

We highly recommend you open a Technical Support Ticket if you have a complex situation and would like to ask questions before updating the PC’s installed version. You can open a Support Ticket here => https://prgress.co/DevToolsSupport.

Hello,

I understand that the team is working hard to support the Report Designer for .NET 8 projects in Visual Studio 2022.  However, may I know whether the Report Designer for .NET Framework 4.8 projects will be supported in Visual Studio 2026?

Thanks.

Deepak Gupta

I'm hoping there's a way to add the additionally supported report export formats such as DOCX, XLSX etc to the Winforms Report Viewer?

I've been able to hide Tiff using the config section, but there seems to be no way (either there or through the Viewer's properties) to allow additional supported formats

Is the only option to hide the export button on the Viewer and implement my own Export?

Hello,

installed a new SDK and got

C:\Users\USER\.nuget\packages\telerik.licensing\1.6.5\build\Telerik.Licensing.targets(29,3): error MSB4216: Could not run the "ResolveTelerikProducts" task because MSBuild could not create or connect to a task host with runtime "NET" and architecture "x64".  Please ensure that (1) the requested runtime and/or architecture are available on the machine, and (2) that the required executable "C:\Program Files\dotnet\sdk\9.0.307\MSBuild.dll" exists and can be run.

Works fine with previous SDK 9.0.306.

Any fix?

I have a requirement to produce reports for archival purposes that can consist of 50K-60K rows.  WPF client app code snippet is:

                tblDetail.NeedDataSource += (s, e) =>
                {
                    var t = (Table)s;
                    t.DataSource = visibleRows;
                };

                var reportProcessor = new ReportProcessor();
                RenderingResult? result = reportProcessor.RenderReport("PDF", report, null);

I have a report with all of the content in a  group header section, all of which fits nicely on one page with one problem. I have a subreport in the content shown here on the designer;

The Subreport is a simple name list with just a detail section (no headers - the waring is that it's not full page width and will be extended horizontally - not what I want, but OK...);

However, it renders like this;

I.e. With a page break before it, with the sub report object (Green) from the main report expanding to full page height, then another page break afterwards and then the rest of the content

I've checked all of the page break settings and they're all set to none - anyone seen anything similar?

Hi, we're looking to integrate Telerik Reporting with a very niche sql database, SAP SQL Anywhere, on dotnet core.  The only way we can connect to that database in dotnet core is System.Data.Odbc and defining the ODBC Driver in the connection string.

Can Telerik Reporting support this method out of the box, or is there a way of writing some glue code to integrate Telerik Reporting with SAP SQL Anywhere?

Happy to answer any clarifying questions.

Appreciate your help.