The background image of a report item is not sized correctly when exporting in PowerPoint format (PPTX) and have the UseMetafile flag set to false.
If the flag UseMetafile is set to true, the image is rendered as expected.

We have an application that is generating very large reports in "Print Preview" mode.

When the first page of the report is generated the Export button gets enabled. If the user does not wait for the report to be fully generated, and clicks the Export button, it doesn't do anything. We have also seen the application crash after clicking the Export button while the pages are loading.

Currently the behavior of the Web Designer and Standalone Designer is different in regard to DateTime Report Parameters and its "Kind" property.
The Web Designer will assume the value is of Kind "Utc" and the Standalone Designer uses "Unspecified".

This recently became more of an issue since the newer PostgreSQL Provider versions are a lot more strict regarding the "Kind" property:
Npgsql: Timestamp rationalization and improvements

The consequence of this is not being able to use Sql parameters which will work in both the WebDesigner/WebViewer and the StandaloneDesigner:

To resolve this issue right now, one would need to resort to ugly workarounds:

• Add a custom function which receives a DateTime "d" and DateTimeKind "k" value and returns the DateTime value "d" with the Kind set to "k"
  • Having to include a user dll to add that function seems overkill
  • You will need to change every report currently in use
• Change the behavior of the WebDesigner to match the behavior of the Standalone Designer by using a custom IReportSourceResolver, manipulating currentParameterValues 
  • The Kind Property is set to "Unspecified" which is arguably the worst option to take between the three

To properly address this issue it needs to be possible to set the Kind property in the Viewer. Or at least the behavior between the WebDesigner and Standalone Designer should be the same.

Additionally/Alternativly it should be possible to set the target Kind in the Report Parameter.

With kind regards,
Dominik Rothert

The R2 2023 Standalone Report Designer for .NET cannot be run with the .NET 7 runtime that previously worked(approach - https://docs.telerik.com/reporting/knowledge-base/how-to-load-dot-net-7-assemblies-in-srd-dot-net).

Error: 'Could not load file or assembly 'System.Configuration.ConfigurationManager, Version=7.0.0.0, Culture=neutral, PublicKeyToken=cc7b13ffcd2ddd51'. The system cannot find the file specified.'

When designing reports with lots of parameters (which is very common for my usage), I often get error message "Missing or invalid parameter value" or "Syntax error in expression". I find it very time consuming and annoying to manually check "all" parameters in order to identify which one is causing the issue. 

Would it be possible to include more details in these error messages, e.g. by including the name of the (first) incorrect parameter? Preferably for the message in report viewer / preview, but at least in the log file.

https://www.telerik.com/forums/missing-or-invalid-parameter-value-please-input-valid-data-for-all-parameters

Reproducible in 17.1.23.606 - SRD and WRD.
Not reproducible with demo report Product Catalog.

Steps to reproduce the behavior:

1. Create new report
2. Add ToC Section
3. Add textbox item
4. Preview the report

Expected behavior
Textbox is shown.

Actual behavior
System.NullReferenceException: Object reference not set to an instance of an object.
at Telerik.Reporting.Processing.DocumentMap.DetermineNodeVisibilityRecursive(BookmarkNode node)
at Telerik.Reporting.Processing.TocSection.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.StackLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.Group.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.StackLayout.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.Report.MeasureContent(IMeasureContext context, SizeLU availableClientSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.VisualElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.ProcessingElement.MeasureCore(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.LayoutElement.Measure(IMeasureContext context, SizeLU availableSize)
at Telerik.Reporting.Processing.LayoutElement.MeasureElement(LayoutElement elementToMeasure, SizeLU availableSize, IMeasureContext context)
at Telerik.Reporting.ImageRendering.ImageReportInteractive.MeasureRootCore(LayoutElement root, PageSettings pageSettings)
at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(LayoutElement root, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback, PageSettings pageSettings)
at Telerik.Reporting.BaseRendering.RenderingExtensionBase.Render(Report report, Hashtable renderingContext, Hashtable deviceInfo, CreateStream createStreamCallback, EvaluateHeaderFooterExpressions evalHeaderFooterCallback)
at Telerik.Reporting.Processing.ReportProcessor.RenderCore(ExtensionInfo extensionInfo, IList`1 processingReports, Hashtable deviceInfo, IRenderingContext renderingContext, CreateStream createStreamCallback)
at Telerik.ReportViewer.Common.ReportRenderer.Render(ReportRendererArgs args)

In Reporting msi installer no verification is performed if the user exists and has create database permissions on remote database SQL server. No message is shown if AdventureWorks database creation fails.

1. Start Reporting .msi installer.
2. Agree with License.
3. Click button "Examples setup".
4. Enter database server name on remote machine with user with only public server role.
5. Click Next.
6. Click Install.

Expected: Message that database creation failed on step 4,5, or 6.
Actual: Installation proceeds and finishes. AdventureWorks database is not created.

 https://feedback.telerik.com/reporting/1597971-report-duplicating-items-from-svg-image-when-exporting-to-pdf?_ga=2.194313453.1154414800.1688345672-1157346896.1665952494&_gl=1*fh25sr*_ga*MTE1NzM0Njg5Ni4xNjY1OTUyNDk0*_ga_9JSNBCSF54*MTY4ODU0MDMwNy4zMzguMS4xNjg4NTQwMzgwLjU4LjAuMA

Hey team,
Please kindly speed up about this bug as this affects the project alot. Also would appreciate for the update.

If I use Microsoft.AnalysisServices.AdomdClient assembly with version 13 or higher, I receive the following exception:

An error has occurred while processing Report 'Report1':
Unable to establish a connection to the database. Please verify that your connection string is valid. In case you use a named connection string from the application configuration file, make sure the name is 
correct and the connection string settings are present in the configuration file of your application.
------------- InnerException -------------
Attempt by security transparent method 'Telerik.Reporting.Adomd.AdomdProviderFactory.CreateConnection()' to access security critical method 'Microsoft.AnalysisServices.AdomdClient.AdomdConnection..ctor()' 
failed.
 
Assembly 'Telerik.Reporting.Adomd, Version=16.0.22.119, Culture=neutral, PublicKeyToken=a9d7983dfcc261be' is marked with the AllowPartiallyTrustedCallersAttribute, and uses the level 2 security 
transparency model.  Level 2 transparency causes all methods in AllowPartiallyTrustedCallers assemblies to become security transparent by default, which may be the cause of this exception

With earlier versions, the data source works as expected.

To have a better performance would be nice to cancel report rendering automatically or manually. 
If I am asking for a big report and after I change parameters and request new report, the previous request is still in progress and it is not going to be cancelled. Therefore I see high memory consumption on continuously refreshing a reports with a big data and after some time I see complete slow down of the Reporting Service and of course slow down of the server itself. The memory in this case is not released and Reporting Service crashes sometimes.

Setting values to the request body in the WebServiceDataSource component via inline parameters turns the values of the string regardless of what is passed in the design/runtime parameter expression.

For example, in the following image, I set the runtime expression to be =2000 which should embed that value as a number to my request's body on previewing the report. Instead, the value is sent as the string "2000":

When Kendo version 2023.1.314 is used, the tooltips of the HTML5 Report Viewer and its wrappers flicker when the cursor hovers above them.

Telerik Reporting Version: 17.0.23.315

Currently the generated accessible PDF documents contain tagged elements, but lack information about the logical structure of the PDF document. This prevents screen readers of correctly reading the PDF document contents. The tools like PAC (PDF Accessibility Checker) do not display correctly the document structure.

Hi Team,

Currently, the Angular Report View doesn't appear to support the Ivy rendering. As of Angular 16 (released 4 days ago), the legacy rendering mode is fully removed. Which means the ReportViewer will no longer work in ng16 or later.

So this feature request is to move the ReportViewer to support Ivy (which will support Angular v9 to v16 and later).

Thank you,

Maks

We have many reports that contain grids using Table controls. We are using the HTML Report Viewer with the enableAccessibility option set to “true” to display these reports to application users. 

Using this configuration, the report when run in a browser generates markup using absolutely positioned DIVs instead of TABLE tags for the grids in the report. The accessibility company provided documentation that the generated report content is in violation of WCAG 2.1 A, 4.1.2, Name Value Role since the generated report content is neither a semantic HTML table nor adheres to the ARIA table pattern. 

Since Reporting Tables are rendered as DIV elements, you need to ensure they implement the following ARIA Design Pattern specifications:

• The table container needs role="table".
• Each row container needs role="row" and to be either a DOM descendant of or owned by the table element or an element with role="rowgroup".
• Each cell must be either a DOM descendant of or owned by a row element and to have one of the following roles: 
  • columnheader if the cell contains a title or header information for the column.
  • rowheader if the cell contains the title or header information for the row.
  • cell if the cell does not contain column or row header information.
• Remove the aria-label from each cell. Following this design pattern, only the element with role="table" should have an aria-label or aria-labelledby value to provide an accessible name.
• If there is an element in the user interface that serves as a label for the table, the table element needs an aria-labelledby property with the value as the ID of the labeling element. Otherwise, a label must be specified for the table element using aria-label.
• If the table has a caption or description, the table element needs an aria-describedby property with the value as the ID of the element containing the description.
• After these remediations, it should no longer be necessary for the cells to be focusable unless they have an interactive function. Removing the tabindex from the cells will also reduce the number of unnecessary tab stops.

The value '姓名：' is rendered on two lines in a TextBox under Linux. The colon symbol at the end '：' appears on the second line no matter how wide is the TextBox. The colon character itself is a special Unicode Character “：” (U+FF1A).

There are other symbols that may be used instead of the colon to reproduce the issue in Linux rendering. Under Windows, the text is rendered as expected.

It will be nice to have a proper (Official) TypeScript definition for the HTML5 Report Viewer. 

When exporting a graph that has multiple line series and a category scale to CSV, the error "object reference not set to an instance of an object" is thrown.

More specifically, the issue occurs when one or more of the series do not have a corresponding non-null value for every category.