Currently, when you set SplitWorksheetOnPageBreak to True, the Excel Sheet name is formed from the DocumentName or ReportName and the number of the page.

It would be very helpful if the report authors can manipulate these names with Expressions.

If you embed an iframe that points to a report viewer on a page, and the page is hosted on a web server on a different origin, the print functionality does not work.

Consider implementing a workaround to enable it.

Hi

Currently, when referencing an assembly from appsettings.json in telerikReporting:assemblyReferences  , the Object Data Source wizard in Telerik Web Reporting displays all namespaces from that assembly, even if only one class is marked with [DataObject]. This results in unnecessary namespace clutter and can confuse report designers, especially in large projects where only a single data object is intended for reporting. See screenshots below:

Please provide a way to control which namespaces and/or classes are visible in the Object Data Source wizard. Possible solutions could include:
•    Only displaying namespaces that contain [DataObject] classes (filtering namspaces with no elments to display)
•    Allowing explicit inclusion/exclusion of namespaces or classes via configuration (e.g., in appsettings.json).
•    Supporting an attribute (such as [Browsable(false)] or a new custom attribute) to hide specific classes or namespaces from the wizard UI.

Thank you for considering this improvement!

I am rendering reports locally using the report processor. When I use the RenderReport method after processing MS Office Documents and PDF files with the Spire. Office, it causes the text of the report rendered with Telerik Reporting to get truncated:

using Telerik.Reporting;

Spire.Doc.Document document = new Spire.Doc.Document();

var wordDocPath = "./wordtest.docx";
var pdfFilePath = System.IO.Path.Combine("../../../", "wordtest.pdf");

document.LoadFromFile(wordDocPath);

Spire.Doc.ToPdfParameterList toPdf = new Spire.Doc.ToPdfParameterList();
//toPdf.AutoFitTableLayout = true;
document.SaveToFile(pdfFilePath, toPdf);
document.Close();

var reportProcessor = new Telerik.Reporting.Processing.ReportProcessor();
var reportPackager = new ReportPackager();

string sourceReportFile = "./Static Broken CSU Analysis.trdp"; ;

using (var sourceStream = System.IO.File.OpenRead(sourceReportFile))
{
    var report = (Report)reportPackager.UnpackageDocument(sourceStream);

    var deviceInfo = new System.Collections.Hashtable();

    var reportSource = new InstanceReportSource();

    reportSource.ReportDocument = report;

    Telerik.Reporting.Processing.RenderingResult result = reportProcessor.RenderReport("PDF", reportSource, deviceInfo);


    if (!result.HasErrors)
    {
        string fileName = result.DocumentName + "." + result.Extension;
        string filePath = System.IO.Path.Combine("../../../", fileName);

        using (System.IO.FileStream fs = new System.IO.FileStream(filePath, System.IO.FileMode.Create))
        {
            fs.Write(result.DocumentBytes, 0, result.DocumentBytes.Length);
        }
    }
}

If I comment out the section that is converting the totally unrelated word file to pdf and run it again, it does not clip.

I’m working on a project that requires generating Section 508-compliant PDFs, and I’m using Telerik Reporting to build the accessible reports. However, I’ve run into a problem with how screen readers—specifically NVDA—are interpreting table content.

In my report’s table, some values like 12/01/2023 aren’t being read as dates, and values like (192,340.00)—which represent negative numbers—aren’t being interpreted as “negative” or addressing the parenthesis.

In the Telerik Reporting Designer there are already quite a few Chart Diagrams included but the one that is missing is a Sankey Diagram. This is already integrated in the Charts in KendoReact for example and I would like to request to also add this in Telerik Reporting because I think it would be a great addition and also we would for sure need this.

Thanks,

Regards,

Bernd

Our clients enter information using the radeditor and in many cases want to embedded tables and graphics into their text.  Using your reporting tool there is no way to print this information.  I know you have suggested using your table and image tools, but that doesn't work when you are dealing with freely formatted text so the existance and location of the tables and images cannot be predicted.

When I drag a data field from a DataSource component to the Report details section in the Standalone Report Designer, the Report > DataSource property is set automatically to the corresponding DataSource component.

In the Web Report Designer, when I drag a data field, the Report > DataSource property remains empty, and the Preview shows an empty report. It would be very helpful the same functionality to be introduced also in the Web Designer.

<dependencies>
  <group targetFramework=".NETFramework4.6.2">
    <dependency id="Newtonsoft.Json" version="13.0.1" />
    <dependency id="Telerik.Reporting" version="[19.0.25.313]" />
    <dependency id="Microsoft.Net.Http" version="2.2.29" />
  </group>
  <group targetFramework=".NETStandard2.0">
    <dependency id="Newtonsoft.Json" version="13.0.1" />
    <dependency id="Telerik.Reporting" version="[19.0.25.313]" />
  </group>
</dependencies>

The package "Microsoft.Net.Http" is with the latest available version and depends on:

Microsoft.Bcl (>= 1.1.10)
Microsoft.Bcl.Build (>= 1.0.14)

The package "Microsoft.Bcl" is indeed deprecated.

With the 2025 Q2 release, the 3-parameter AddTelerikReporting static method was replaced with a 4-parameter method containing an additional argument for the optional AIClientFactory method of the REST Service.

The original method should be returned to avoid breaking projects that do not implement an AIClientFactory.

The property UserIdentity.Current is decorated with a [ThreadStatic] attribute, that guarantees a new instance will be created per each thread, when used in a synchronous context.

In asynchronous context, e.g. when an await operation is performed, the current thread is released, and another thread from the thread pool may take over. This can lead to the UserIdentity being overridden or conflicting with another request.

I often need to have the same Report Parameters in different reports, including the main and its subreport. Currently, I need to add the parameters manually.

It would be very useful if we could copy/paste Report Parameters between reports.

I set globally the culture on the Linux Ubuntu Docker Container. Interestingly, the negative currency with en-US and fr-CA was displayed with the '-' sign rather than in brackets.

This was reproduced even in the values set with the Text Function FormatWithCulture(cultureName, format, args). The function displayed wrong formatting also on Windows, even in the Standalone Report Designer for .NET 8.

When the global culture on Windows was en-US, the negative decimal value formatted without the FormatWithCulture function was displayed correctly in .NET 8.

In the .NET Framework, the negative currencies were displayed as expected in all scenarios.

I have linked also a muted video showing the issue.

I have projects on .NET Core and I want to use the System.Text.Json serializer that is the new default, but reporting relies on Newtonsoft.Json.

---

ADMIN EDIT

There are two approaches that can be taken right now to solve this:

OPTION 1: define separate endpoints (services, projects) for the different tasks - they can still use the same database layer through a shared project, depending on the architecture you have. This would let you have separated services with the appropriate serializers without custom attributes and code (see below). For example, create a separate project for the reporting REST services.

OPTION 2: add some custom decoration on the endpoints so you can choose which serializer is used on each, you can find some examples here: https://stackoverflow.com/questions/59650907/how-to-configure-two-json-serializers-and-select-the-correct-one-based-on-the-ro - the point being to register a serializer depending on the endpoint based on your own code rather than let the framework put one in for all endpoints.

NOTE: This would be a breaking change.

---