Currently, when using External Stylesheets in the reports, the engine tries to first load the stylesheet as an embedded resource of the assembly. If it fails to load it from the assembly, a message is written to the trace along the lines of:

ESS: Attempt to load ExternalStyleSheet from EmbeddedResource from assembly Telerik.Reporting, Version=19.0.25.211 with resource name styles.xml is unsuccessful.

After this, the engine will try other ways to resolve the stylesheet such as from URI and if it succeeds, the report will render as expected.

This can create confusion because looking at the trace, one might think that there were errors with the rendering of the report because the stylesheet did not load but it was actually successfully loaded with one of the other approaches.

It would be better to write the errors to the trace only if the stylesheet does not load after all attempts.

When the parametersAreaVisible property of the report viewer is set to true, the parameters area of the viewer should be open by default if a report that has visible parameters is being previewed.

However, when a mobile device is used, the parameters area is closed by default.

Additionally, the arrow used to open the parameters area is hidden by default. The device orientation needs to be toggled to horizontal and back for the arrow to appear.

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.

I have a .NET project. I tried to add a CS-based report to it using the Visual Studio item template. However, when I opened it, I encountered an error message, which wasn't helpful.

After reaching out to the technical support, I was told that the Visual Studio Report Designer was not supported in .NET projects, and the alternative was either to open the CS-based report through the Standalone Report Designer or use TRDP reports (recommended for new reports) instead.

It would be nice if there were some warning about this, as it would save me some time and confusion, as at first, when I encountered the error message, I took the assumption that something was corrupted with my project.

When the current thread culture is set to Turkish (tr-TR), the lowercase and uppercase conversion rules differ from English — especially for the letter "i".

• In Turkish:

  • "i".ToUpper() → İ (with a dot)

  • "I".ToLower() → ı (dotless i)

Our assumption that the Telerik HtmlTextBox internally parses and maps HTML tags by converting them to uppercase. When the Turkish culture is active, this conversion causes tag names to break, which is not a valid tag, so ordered lists fail to render.

Best regards,
Denis

The Telerik Web Forms Report Viewer Form VS item template does not install the Telerik.Reporting.Services.WebApi package. However, the controller created with this template has a using statement for it.

Steps To Reproduce

1. Create a new Web Forms project.
2. Right click on the project name > Add > New Item...
3. Choose Telerik Web Forms Report Viewer Form <REPORTING_VERSION>.
4. Build the project.

Expected behavior
The build succeeds.

Actual behavior
The build fails due to the missing package.

Screenshots

The data source of my report contains grouping string values, among which are the '10000' and '1010Q'. These two values are always treated as the same string, and the corresponding records fall within the same report group, which is unexpected:

WebReportDesigner (Blazor) - permission to restrict "Build new data connections" and allow to use only "Select from existing data connections".

It isn't required, but would be nice have button "Test connection" in the bottom enabled to verify predefined connection

Use SqlDataSource SelectCommand xml element instead xml attribute - it allows to write complex sql requests in any tool and just put it into xml without changes and have it well-formatted and readable:

So, instead of

save it as

or even

In the latest Reporting version, the interface of the report viewer allows users to set the value of a multiselect report parameter to an empty collection but not make it null.

In some scenarios, reports rely on parameters being null to filter their data and this makes them unusable in the latest version.

Images taken with a mobile device are sometimes displayed in PictureBox  rotated by 90, 180 or 270 degrees. The reason is that whenever a photo is taken, the device saves its current accelerometer orientation into a corresponding Exif tag with the image metadata, so this info is then read and taken into account by our Report Designer.

ADA Accessibility is a priority for our customers, so we are aiming to ensure logical tabbing order for keyboard users.

I've noticed that the RowHeadersPrintOnEveryPage attribute, while very useful for creating more readable PDF exports, seems to result in some strange screen reader behavior when set to True.

The first problem is with the strange tabbing order in the live environment. The second column header is the first to receive focus, followed by the remaining column headers, then the data fields under the first column receive focus in a vertical list, until finally the first column header receives focus. Without the default RowHeadersPrintOnEveryPage setting (False), the first column header is the first to receive focus, which is expected. 

In addition to the wrong tabbing order, the RowHeaderPrintOnEveryPage causes the screen reader to announce the incorrect column associated with a particular cell. I use the Windows Narrator. Other screen readers may result in slightly different behavior. 

When the WinForms Report Viewer is initialized from within the Form.Load Event, and the RefreshReport() method of the viewer is invoked before it is added to a parent form, the following exception will be thrown: 

Telerik.ReportViewer.WinForms.Licensing.UiLicensePresenter.ShowWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.Common.TelerikLicensePresenterBase.PresentWatermark(Action showWatermarkCallback)
   at Telerik.ReportViewer.WinForms.WinViewer.OnPaint(PaintEventArgs eventArgs)
   at System.Windows.Forms.Control.PaintWithErrorHandling(PaintEventArgs e, Int16 layer)
   at System.Windows.Forms.Control.WmPaint(Message& m)
   at System.Windows.Forms.Control.WndProc(Message& m)
   at System.Windows.Forms.Control.ControlNativeWindow.WndProc(Message& m)
   at System.Windows.Forms.NativeWindow.Callback(HWND hWnd, MessageId msg, WPARAM wparam, LPARAM lpa

Currently, the is permission for disabling saving, but it disables only the "Save" button.

I would like to be able to disable the "Save As" button and keep the "Save" button active, or vice-versa.

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.