29 Jan to 05 Feb 2026: highlights of the new online resources that we published last week.

Article: https://www.telerik.com/products/reporting/documentation/introduction
Summary: Learn how to design, process, and embed Telerik Reporting in your .NET applications: available report designers (Standalone, Visual Studio, Web), report definition formats (.trdp, .trdx, code), viewers for ASP.NET Core/MVC, HTML5, WPF, and WinForms, the REST service, supported data sources (SQL, Entity Framework, JSON, CSV, web services), and export formats (PDF, Excel, Word, PowerPoint, HTML, images). The page also defines core concepts—parameters, expressions, styling, and interactive actions (drill-down, drill-through)—and outlines system requirements and integration paths.

Article: https://www.telerik.com/products/reporting/documentation/knowledge-base
Summary: Use the Telerik Reporting Knowledge Base to quickly troubleshoot and implement reporting scenarios: data source setup, parameters and expressions, layout/styling, rendering/export/printing, performance, licensing, and common error messages. It provides code and configuration examples for integrating viewers and the REST service (HTML5, Blazor, ASP.NET Core, Angular, React, WPF, WinForms), configuring the Web Report Designer, and deploying to IIS, Azure, or Docker on .NET Framework and .NET 6/7.

Article: https://www.telerik.com/products/reporting/documentation/upgrade/overview
Summary: This article explains how to upgrade Telerik Reporting projects, covering NuGet-based setups, direct assembly references, report viewers, the REST service, and report definitions. You are guided to review release notes for breaking changes, back up your solution, then either run the Visual Studio Upgrade Wizard or update all Telerik Reporting NuGet packages to the same version; update all viewers and the REST service to match, replace viewer assets, adjust web.config/app.config binding redirects, and rebuild. Keep the engine, designers, viewers, and services on the same version; the Standalone/VS designers will upgrade older .trdp/.trdx or code-based reports when opened.

Article: https://www.telerik.com/products/reporting/documentation/report-items/panel
Summary: Learn how to use the Telerik Reporting Panel report item as a container to group and position child report items with a local coordinate system. The article shows how to add and nest items, configure size, borders and background, apply container-level bindings, styles, actions, and visibility, and how the Panel participates in rendering and paging (including keeping grouped content together and enabling drill-down/collapsible sections). Use a Panel when you need to move, show/hide, or style multiple report items as a unit or to build composite layouts like headers or address blocks.

Article: https://www.telerik.com/products/reporting/documentation/report-items/shape
Summary: This article explains how to use the Shape report item in Telerik Reporting to draw simple geometric elements (lines, rectangles, ellipses) for separators and emphasis. You add the item in the designer and configure ShapeType, size and location, rotation (Angle), and styling (fill and borders), with the option to bind these properties to expressions for dynamic visuals.

Article: https://www.telerik.com/products/reporting/documentation/user-guide/app-tour
Summary: This article provides an overview of the Telerik Reporting Standalone Report Designer UI, including the ribbon, toolbox, design surface, Report Explorer, Group Explorer, Property Grid, Data and Parameters panes, Error List, and Preview. You learn where to create/open reports, connect data sources, add and configure report items, manage groups and styles, and preview/export so you can navigate the designer efficiently during report development.

Article: https://www.telerik.com/products/reporting/documentation/report-items/textbox
Summary: Use the Telerik Reporting TextBox report item to render static or data-bound text, numbers, and dates by setting the Value expression and optional .NET Format in sections, panels, or table cells. The article shows you how to configure style and layout (alignment, padding, TextWrap, Angle, CanGrow/CanShrink), add expressions and bindings for dynamic properties, apply conditional formatting, and wire interactive actions (hyperlink, drill-through/toggle). For HTML-formatted content, use HtmlTextBox instead.

Article: https://www.telerik.com/products/reporting/documentation/upgrade/2013/q3-2013
Summary: Use this upgrade guide to move your projects to Telerik Reporting Q3 2013: update all Telerik.Reporting and report viewer assembly references, adjust web/app.config settings, and recompile. It outlines breaking changes and obsolete APIs, notes report definition and viewer control updates across ASP.NET, WPF, WinForms, and Silverlight, and provides migration steps to resolve compile- and runtime issues.

Article: https://www.telerik.com/products/reporting/documentation/upgrade/2014/q1-2014
Summary: This article shows you how to upgrade existing projects to Telerik Reporting Q1 2014 by updating all Telerik.Reporting and report viewer assembly references, applying the required app/web.config sections and handlers, and rebuilding. It lists the breaking changes and concrete migration steps for report definitions and the ASP.NET WebForms/MVC, WPF, and Silverlight report viewers so you can replace deprecated APIs, fix namespace/config differences, and get the project running after the update.

Article: https://www.telerik.com/products/reporting/documentation/upgrade/2014/q2-2014
Summary: This article shows you how to upgrade existing projects to Telerik Reporting Q2 2014 by updating all Telerik.Reporting assemblies, adding binding redirects, and adjusting project and web.config settings. It details viewer-specific steps (ASP.NET WebForms, MVC, HTML5) including configuring the Reporting REST service or handler/route registrations, and lists the breaking API and configuration changes you must fix (renamed/obsolete APIs, updated rendering/export extensions) to recompile and run successfully.

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

19 Jan to 26 Jan 2026: highlights of the new online resources that we published last week.

Article: https://docs.telerik.com/reporting/upgrade/2025/2025-q4-19-3-26-121
Summary: This article guides you through upgrading to Telerik Reporting 2025 Q4 (version 19.3.26.121), with step-by-step instructions for updating NuGet packages, rebuilding, and validating reports across .NET targets. It summarizes migration notes—such as any API or behavior changes, dependency updates, and viewer/designer compatibility—so you can resolve compile-time errors and runtime differences during the upgrade.

Article: https://docs.telerik.com/reporting/designing-reports/troubleshoot-report-definition-tips
Summary: Use this guide to systematically troubleshoot Telerik Reporting report definitions, including “The report definition is invalid” errors during preview or rendering. You’ll learn how to read processing/rendering error details and inner exceptions, validate expressions and bindings, verify data source fields and parameter types, and resolve version or assembly reference mismatches between the designer, runtime, and viewers. It also outlines common failure patterns (null references, missing fields after schema changes, invalid aggregates, style/resource lookups) and where to collect diagnostics (Designer preview, Visual Studio Output window, trace logs, IIS).

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

05 Jan to 12 Jan 2026: highlights of the new online resources that we published last week.

Article: https://docs.telerik.com/reporting/knowledge-base/aspnet-webforms-website-resolving-invalid-license-watermark
Summary: Learn how to remove the “Invalid license” watermark in the WebForms Report Viewer when running an ASP.NET Web Site (no .csproj) by providing the Telerik UI for ASP.NET AJAX license key at runtime. You’ll add the key either in web.config appSettings (key: Telerik.Web.UI.LicenseKey) or as a plain text file named Telerik.Web.UI.LicenseKey in the site root, then redeploy and clear Temporary ASP.NET Files/app pool to apply it. The article also reminds you to ensure commercial (not trial) assemblies are deployed to prevent report trial watermarks.

Article: https://docs.telerik.com/reporting/knowledge-base/cannot-load-telerik-reporting-chart-type
Summary: If you hit “Cannot load type 'Telerik.Reporting.Chart'” at runtime, your report still uses the legacy Chart item that is no longer included in recent Telerik Reporting versions or there’s a version mismatch between your report definition and runtime assemblies. Replace the Chart with the Graph report item (use the designer’s conversion tool) or run the report with a Telerik Reporting version that still supports Chart. If you can’t migrate immediately, ensure all Telerik Reporting assemblies and binding redirects are aligned to the same version to avoid type-loading errors.

Article: https://docs.telerik.com/reporting/knowledge-base/fixing-imvcbuilder-errors-telerik-reporting-rest-service
Summary: You’ll fix IMvcBuilder compile errors that occur when configuring the Telerik Reporting REST Service in ASP.NET Core (Startup.cs or .NET 6/7 Program.cs). The article shows which packages to install or align (notably Microsoft.AspNetCore.Mvc.NewtonsoftJson), how to chain AddControllers/AddMvc so IMvcBuilder extension methods resolve, and provides working code for minimal hosting and classic Startup—addressing missing AddNewtonsoftJson, extension method, and using/namespace issues.

Article: https://docs.telerik.com/reporting/knowledge-base/send-email-inputs-validation-error
Summary: Explains why the Send Email dialog in Telerik Reporting (e.g., HTML5 Report Viewer) throws input validation errors and how to fix them. You’ll learn the required format for To/CC/BCC (RFC-compliant addresses, comma-separated for multiple recipients), common rejection causes (invalid characters, spacing, separators), and options to resolve them by correcting inputs or overriding the dialog’s validator if you need different rules.

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

15 Dec to 22 Dec 2025: highlights of the new online resources that we published last week.

Article: https://docs.telerik.com/reporting/knowledge-base/adjusting-currency-formatting-csv-export-reporting
Summary: Learn how CSV export in Telerik Reporting is data‑oriented and ignores TextBox.Format/Style, so you’ll get raw numeric values without currency symbols or locale-specific separators by default. You’ll format currency for CSV by emitting a string from the TextBox.Value (for example, using Format/CultureInfo or setting the report Culture) to include symbols and separators. The article also notes the trade‑off: once formatted as strings, these CSV fields may be treated as text by tools like Excel, affecting numeric calculations.

Article: https://docs.telerik.com/report-server/dotnet-docs/token-authentication 
Summary: Telerik Report Server for .NET, from 2025 Q4, empowers users to generate JWT-based Personal Tokens for secure, remote authentication in Report Viewers, bypassing username/password logins. Users create expiring tokens via the Manager, which trigger short-lived access and refresh tokens for seamless sessions. Admins manage Guest User tokens for sharing reports externally through auto-generated links, ensuring reading-only permissions and easy control.

Article: https://docs.telerik.com/reporting/ai-coding-assistant/mcp-server-as-a-nuget
Summary: Learn how to add and host the Telerik Reporting Model Context Protocol (MCP) server as a NuGet package in a .NET application to enable the AI Coding Assistant with MCP-compatible clients. The article covers installing the package, wiring the server into a host/DI setup, configuring required options (license, report engine, allowed roots/report sources), and running the server for clients such as Claude Desktop. It includes a minimal Program.cs example and client configuration guidance to let the assistant read and modify report definitions safely.

Article: https://docs.telerik.com/reporting/knowledge-base/removing-bar-border-in-graph
Summary: Shows how to remove the default border/outline from bars in a Telerik Reporting Graph by styling the bar data points rather than the series. Set BarSeries.DataPointStyle.BorderStyle=None (or BorderWidth=0, BorderColor=Transparent) in the report designer or in code so bars render without borders.

Article: https://docs.telerik.com/reporting/knowledge-base/rendering-layered-date-range-backgrounds-telerik-reporting-table-cells
Summary: This article shows you how to render layered date‑range backgrounds in Telerik Reporting Table cells by generating the background as an image at runtime and binding it to a PictureBox. You implement a custom user function that takes the cell’s time window and a list of date ranges, draws semi‑transparent layers on a bitmap (returning Image/byte[]), bind it via an expression (Sizing=Stretch), and optionally overlay text to achieve Gantt‑like or booking overlays per cell.

Article: https://docs.telerik.com/reporting/knowledge-base/rendering-markdown-in-telerik-reporting-templates
Summary: This article shows you how to render Markdown in Telerik Reporting by converting it to HTML and displaying it in an HtmlTextBox. You create a C# user function (for example, using Markdig) to transform Markdown to HTML, call it from report expressions, and register/deploy the helper assembly for the Standalone Report Designer and the report runtime. It also notes the HtmlTextBox’s supported HTML/CSS subset so you can anticipate which Markdown constructs will render.

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

01 Dec to 08 Dec 2025: highlights of the new online resources that we published last week.

Article: https://docs.telerik.com/reporting/knowledge-base/resolving-svg-rendering-issues-telerik-licensing-telerik-reporting
Summary: Learn why SVG images can appear blank or fail to render in Telerik Reporting after enabling Telerik Licensing with the NuGet/MSBuild build tasks. The article shows you how to fix the issue by updating to a version that addresses the problem and configuring your build to exclude SVG files from licensing processing (or relocating them), ensuring consistent SVG rendering in viewers and exports.

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

24 Nov to 01 Dec 2025: highlights of the new online resources that we published last week.

Article: https://docs.telerik.com/reporting/knowledge-base/adjusting-textbox-spacing-layout-telerik-reporting
Summary: This article shows how to control TextBox spacing and layout in Telerik Reporting using Style.Padding (Top/Right/Bottom/Left), borders, and precise item sizing/positioning, instead of inserting spaces or blank lines. It explains how CanGrow/CanShrink and TextWrap affect whitespace and consistency across renderers (HTML, PDF, Excel), and when to use an HTMLTextBox with CSS (margin, line-height) if you need paragraph or line spacing that the standard TextBox does not provide.

Article: https://docs.telerik.com/reporting/knowledge-base/fixing-missing-ai-powered-insight-icon-telerik-report-viewer
Summary: This article shows how to fix a missing AI Powered Insight icon in the Telerik Reporting HTML5 Report Viewer: verify version compatibility, load the correct viewer scripts/styles and icon assets, and enable AI Insights in the Reporting REST service and viewer configuration. You’ll also check toolbar customization and resource paths that commonly hide the button to ensure the icon renders and the feature works at runtime.

Article: https://docs.telerik.com/reporting/knowledge-base/rendering-large-reports-telerik-reporting-docker-pods
Summary: Learn how to render large Telerik Reporting documents inside Docker/Kubernetes pods by right-sizing container memory/CPU and aligning .NET’s container-aware GC with your resource limits. The article shows how to configure the Reporting REST service to use a persistent volume for its cache/temp storage and tune Kubernetes requests/limits to prevent OOMKill when exporting heavy formats like PDF/XLSX. You’ll also get guidance on monitoring memory usage per report and scaling pods to handle high-volume workloads.

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

17 Nov to 24 Nov 2025: highlights of the new online resources that we published last week.

Article: https://docs.telerik.com/reporting/upgrade/2025/2025-q4-19-3-25-1119
Summary: This article shows you how to upgrade your projects to Telerik Reporting 2025 Q4 (version 19.3.25.1119), including updating NuGet packages and assembly references for the reporting engine and viewers (ASP.NET Core, MVC, WPF, WinForms) and applying necessary configuration changes. It calls out breaking changes and deprecations, clarifies supported .NET and Visual Studio versions, and provides guidance to resolve common compile-time and runtime issues after the upgrade.

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

 

10 Nov to 17 Nov 2025: highlights of the new online resources that we published last week.

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.

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

 

29 Oct to 05 Nov 2025: highlights of the new online resources that we published last week.

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.

Hi. My Client has a very old version of Telerik Reports and I need to do some adjustments. I went to my product page to try and download an earlier version, but, it doesn't seem to go back quite this far (currently 10.0.16.13)

Is there anyone I can contact to try and get the version: Telerik report 7.0.13.426 (Q1 2013) or am I looking in the wrong place on the Download Page?

Many thanks

Chuck

Hi 

I am using Telerik web reporting, and its givingan undefined isValid error on my web reporting designer.

 

Using Asp.net core, c# with front end react application

.NET SDK: Version:           9.0.304

React 18

Also getting this confgration errror from => http://localhost:{port}/api/reportdesigner/configuration

{

    "message": "An error has occurred.",
    "exceptionMessage": "Method 'CLIMessage' in type 'RuntimeInvalidLicenseStatus' from assembly 'Telerik.Reporting, Version=19.1.25.521, Culture=neutral, PublicKeyToken=a9d7983dfcc261be' does not have an implementation.",
    "exceptionType": "System.TypeLoadException",
    "stackTrace": "   at Telerik.Reporting.Common.LicenseValidator.Init()\r\n   at Telerik.Reporting.Common.LicenseValidator.CreateInstance()\r\n   at System.Lazy`1.ViaFactory(LazyThreadSafetyMode mode)\r\n--- End of stack trace from previous location ---\r\n   at System.Lazy`1.CreateValue()\r\n   at Telerik.Reporting.Common.LicenseValidator.get_Instance()\r\n   at Telerik.Reporting.Services.Engine.ReportEngine.GetConfiguration()\r\n   at Telerik.Reporting.Services.AspNetCore.BusinessLogic.ReportsBusinessLogic.GetConfigurationInternal(IReportServiceConfiguration reportServiceConfiguration)\r\n   at Telerik.Reporting.Services.AspNetCore.ReportsControllerBase.GetConfiguration()\r\n   at lambda_method2(Closure, Object, Object[])\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ActionMethodExecutor.SyncActionResultExecutor.Execute(ActionContext actionContext, IActionResultTypeMapper mapper, ObjectMethodExecutor executor, Object controller, Object[] arguments)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeActionMethodAsync()\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeNextActionFilterAsync()\r\n--- End of stack trace from previous location ---\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Rethrow(ActionExecutedContextSealed context)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.Next(State& next, Scope& scope, Object& state, Boolean& isCompleted)\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ControllerActionInvoker.InvokeInnerFilterAsync()\r\n--- End of stack trace from previous location ---\r\n   at Microsoft.AspNetCore.Mvc.Infrastructure.ResourceInvoker.<InvokeNextExceptionFilterAsync>g__Awaited|26_0(ResourceInvoker invoker, Task lastTask, State next, Scope scope, Object state, Boolean isCompleted)"
}

Hello,

I have the following scenario and would like guidance on how to achieve the desired behavior.

I have a panel that contains:

• some common elements (for example, a title and metadata textboxes), and

• an outer list, which itself contains an inner list.

The data source has the following structure (simplified):

[
  [
    { "Text": "exampleText1", "Value": 1 },
    { "Text": "exampleText2", "Value": 2 },
    { "Text": "exampleText3", "Value": 3 }
  ],
  [
    { "Text": "exampleText21", "Value": 1 },
    { "Text": "exampleText22", "Value": 2 },
    { "Text": "exampleText23", "Value": 3 }
  ]
]

The outer list is bound to the main data source.
The inner list uses a data source binding like:

DataSource = Fields.Item

The panel that contains the lists also includes common elements (title, metadata) that should only be visible when there is data.

The issue I am facing is related to visibility:
I would like to hide the entire panel (including the common elements) when there are no elements at all in the data structure (for example, when the outer list is empty or when it does not contain any inner items).

I have already tried the following approach:

• creating a report parameter bound to the data source,

• attempting to evaluate a condition such as Count(Fields.Item) > 0,

• setting the parameter to true or false based on that condition,

• and then binding the panel’s Visible property to this parameter.

However, I was not able to make this approach work as expected.

Could you please advise on the recommended way to detect this condition and properly control the panel’s visibility in this scenario?

Thank you in advance for your help.

Best regards,
Balazs

Hey,

I'm currently trying to use the crosstable in a new Report.
In it I have 3 Row Groups and 1 Column Group.

I now want, bigger lines when the row groups change.
So a 3pt Line when next day and a 2pt line when next "Lager".

The problem is I dont get it done as soon as I have a column group.

I tried a lot of different variatons of the example with Previous, I tried Exec.
But still not even a bit achieved what I want.

With this: Exec('value', 'group0', Fields.Ladetag) I get the value of the Ladetag of the current row group.
But to achieve what I want, I would also need the value of the Previous row of the group. 
And here I'm lost.
I cant combine Previous and Exec.
I read abous user functios but what could I pass it...

Maybe someone has an idea.

Greetings,

Benedikt

I am trying to create a report that when I put a sub report on it, the sub report causes objects or fields to move. Researching the problem I have read a lot about margins making sure everything fits. I have done everything I can think of. My sub report width if 5.5 inches. I have made the sub report margins to zero. but still moving objects like it does no have room. I have attached a screenshot of the report in print preview mode along with my report and sub report. please tell me what's wrong, i feel it something easy

just need to confirm if I have to add the Telerik.Drawing.Skia package to my C# .NET Core (9.0) API to fix the error I'm getting when I test the Telerik Swagger endpoints after we deployed to AWS. The container is AWS Linux.

 

This is the error I'm seeing when I use the swagger endpoints that do not need any parameters set, like

https://reportsapi.qa.epidev.net/api/Reports/configuration

https://reportsapi.qa.epidev.net/api/Reports/clients/sessionTimeout

etc.

{
"message": "An error has occurred.",
"exceptionMessage": "Cannot load assembly Telerik.Drawing.Skia. Make sure it is accessible in the current application domain.",
"exceptionType": "DrawingFactoryUnavailableException",
"stackTrace": null
}

I have an old VB.NET(.NET8) winforms app which loads some resources on sign in using 

Image.FromFile("resources\\myImage.png"

This is loaded from the resources sub folder in the runtime directory - so far so good. I also allow the user to change the "focus" of the application, which loads a different image, again so far so good - all of the images are correctly found.

However, if I show the Winforms report viewer, the Directory.CurrentDirectory is reset from the correct runtime folder to the folder which contained the report (which is a UNC share)

This means that loading the images fails - it's looking in the reports directory rather than the runtime directory.

Any one have any ideas on how to solve this?