Declined
Last Updated: 29 Nov 2022 09:37 by ADMIN
Created by: Patrick
Comments: 1
Category: Reporting
Type: Feature Request
0

Hi,

Have the possibility to have the "Select Case" or "Switch" function in the expressions.

Thanks!

Unplanned
Last Updated: 22 Nov 2022 09:30 by OneDealer

We separated our data objects into a library project and then referenced it via the web.config. It works as intended, both in the designer and during data retrieval, but to update the dll with more objects we have to restart the whole site.

It would be very useful if we could substitute our assemblies without restarting the website.

Unplanned
Last Updated: 28 Nov 2022 14:49 by ADMIN
Created by: Danilo
Comments: 0
Category: Reporting
Type: Feature Request
1

The Telerik.Reporting.Report class has the property ExternalStyleSheets which is an ExternalStyleSheetCollection.

This collection consists of objects of the type ExternalStylesheet which has private Name and ResourceKind properties.

Would be great and make sense to make these properties public since that would help when the external stylesheets need to be resolved dynamically, though a custom IReportSourceResolver for example.

Unplanned
Last Updated: 15 Nov 2022 13:39 by Pinou

I want to export a Report as a PNG image with transparent background.

I set the Style > Background to Transparent for the PictureBox in the detail section, for the Page and Detail sections, for the Report itself, and for Report > PageSettings. The PNG image is still rendered with white background.

Unplanned
Last Updated: 08 Nov 2022 14:40 by Dave

We use Reporting REST Service to generate our reports. When exporting to BMP, EMF, GIF, JPEG, and PNG which are all multi-document formats, the downloaded documents are corrupted and cannot be opened in Image viewer.

The TIFF image, which is a single document is exported and opened as expected.

Completed
Last Updated: 18 Jan 2023 11:55 by ADMIN
Release R1 2023

Using the Npgsql data provider of version 6.0.7 leads to the following error when there is a DateTime SQL parameter:

Can't write CLR type System.String with handler type TimestampTzHandler or Can't write CLR type System.String with handler type TimestampHandler.

This error is thrown only on Design-Time because the Design-Time value for the SQL parameter does not respect its selected DbType and is instead always a string.

Unplanned
Last Updated: 07 Nov 2022 12:20 by Mauricio Noguera

My report contains emojis, and they are displayed properly in the designer and in the Html5 Viewer.

When I export to PDF, the emojis disappear. The emoji font is listed as embedded in the PDF file. Even if I embed the full font, the emojis are not displayed.

Unplanned
Last Updated: 01 Nov 2022 11:33 by Thomas
Specifying an invalid data provider or failing to resolve a custom data provider for a SqlDataSource doesn't lead to an exception or even logging the problem in the trace. The Reporting engine simply tries to use the default System.Data.SqlClient and if it fails, the error from the SqlClient provider may be misleading like indicating an invalid connections string: "Exception: System.ArgumentException: Keyword not supported: 'authentication'"
Unplanned
Last Updated: 31 Oct 2022 12:00 by n/a
Created by: n/a
Comments: 0
Category: Reporting
Type: Bug Report
1

I am using the following Telerik configuration section in the Standalone Report Designer:

<Telerik.Reporting>
	<extensions>
        <render>
            <extension name="IMAGE" description="JPEG">
                <parameters>
                    <parameter name="OutputFormat" value="JPEG"/>
                </parameters>
            </extension>
        </render>
    </extensions>
</Telerik.Reporting>

When I try to render a report with multiple pages in JPEG, I receive the error message:

IMAGE rendering extension creates more than one stream. To render, please use the 'bool RenderReport(string format, IReportDocument reportDocument, Hashtable devicelnfo, CreateStream createStreamCallback, out string documentName)' overload instead. 

 

Unplanned
Last Updated: 04 Nov 2022 15:13 by ADMIN
Created by: Ed
Comments: 1
Category: Reporting
Type: Bug Report
1

I am using the HTML Report Viewer and have a report with a parameter that renders as a combobox in the parameter panel of the report viewer.  The tab order of the report parameters do not follow the display order of the parameter fields, specifically any parameter fields that use comboboxes.

An example of this behavior is in the "Employee Sales" report on the Telerik Reporting demo site (https://demos.telerik.com/reporting/employee-sales).  In the report there are 2 parameters, one for Report Date (using a date picker control) and another for Employee (which uses a combobox).  The report viewer is configured to use the combobox option for viewing single and multi selects:

    parameters: {
        editors: {
            singleSelect: telerikReportViewer.ParameterEditorTypes.COMBO_BOX,
            multiSelect: telerikReportViewer.ParameterEditorTypes.COMBO_BOX
        }
    }

When rendered, the Report Date input has a tab index of 301 whereas the Employee combobox has a tabindex of 0.  This results in the tab order of the parameter inputs to not follow the order in which they appear. 
        
I have found that if the above settings are commented out, the tab order of the parameter fields works as expected, but results in a list view control instead of a combobox which is not desirable.

Is it possible to override the tabindex of a combobox parameter input to be set to a tabindex value that is relative to its siblings (i.e., 302) so that tabbing through the fields via keyboard is more natural?

Unplanned
Last Updated: 04 Nov 2022 13:28 by ADMIN
Created by: Syed
Comments: 1
Category: Reporting
Type: Feature Request
1

We can use Telerik UI components with gRPC service however, Telerik reporting service and HTML 5 viewer do not support gRPC.

With gRPC use growing among the developers, we would like to see Telerik reporting support gRPC out of the box.

Completed
Last Updated: 09 Jun 2023 06:36 by ADMIN

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.
Unplanned
Last Updated: 26 Oct 2022 11:18 by Coder
Created by: Coder
Comments: 0
Category: Reporting
Type: Feature Request
1

Add the "Not In" operator for the Filter rules - Filter Rules - Telerik Reporting.

 

Unplanned
Last Updated: 25 Oct 2022 10:51 by Manuel

Currently, when I create a report with the Standalone Designer and localize it, I can preview it only with the language of the machine where I run the designer.

It would be very helpful to have the option to select one of the languages I have set up during localization when previewing.

Unplanned
Last Updated: 24 Oct 2022 13:29 by Graeme

In my report, there are multiple stacked Panels. Each of them may fit on a single physical page. They all have KeepTogether set to True and I expected each of the Panels to start on a new page as two of them cannot fit on one page. This may not happen when I have Page sections though.

When I delete the PageHeader and/or PageFooter the Panels are displayed as expected. However, if I set the Visible of the Page sections to False, the problem persists.

It looks like the Page section's Height is taken into account when evaluating the KeepTogether behavior even for the pages where it is hidden. This shrinks the available physical area and the Reporting engine decides that the Panel cannot fit there, hence the next Panel starts from the current page rather than the next page as I think is correct.

Unplanned
Last Updated: 20 Oct 2022 11:38 by Eric

I have a table with a dark background. In some scenarios, one or more data source fields may be empty, leaving the corresponding table cells with no content. When I export this report to DOCX, the empty cells contain strange white lines.

In the other export formats, the issue does not occur.

Here is how the table looks like in Word:

Completed
Last Updated: 19 Jun 2024 08:47 by ADMIN
Release R3 2022 SP1
1. Start HTML5 or Blazor viewer or designer in a .NET7 RC1 application

Expected: Report Catalog report shown.
Actual: Error creating report instance (Report = 'Report Catalog.trdp'). An error has occurred. A possible object cycle was detected. This can either be due to a cycle or if the object depth is larger than the maximum allowed depth of 64. Consider using ReferenceHandler.Preserve on JsonSerializerOptions to support cycles. Path: $.
Completed
Last Updated: 09 Nov 2022 13:30 by ADMIN
Release R3 2022 SP1
There is a behavioral difference between .NET Framework and .NET assembly loading, which results in inconsistent behavior in the .NET EUD. Currently, referenced assemblies can only be loaded by file name. (i.e. MyAssembly should be passed as MyAssembly.dll in the config). The former behavior (loading by name) should be enabled for better consistency.
Unplanned
Last Updated: 22 Jan 2024 08:00 by ADMIN
Created by: Liam
Comments: 0
Category: Reporting
Type: Feature Request
1
Option to select all data source fields During a table/graph wizard rather than having to select each column individually
Completed
Last Updated: 09 Nov 2022 13:30 by ADMIN
Release R3 2022 SP1

In the Web Designer, I can create OhlcSeries but I cannot find a way to provide the OHLC marks. Whatever I enter for Y value, in the Design view I see the error "The XML serializer cannot resolve type with name: Telerik.Reporting.OhlcMarks". In Preview the error is "An error has occurred while processing Graph 'graph1':ohlcSeries1: OHLC values value cannot be null or empty when using NumericalScale".
If I created an OHLC chart with the Standalone Designer and opened it in the Web Designer, the Y value would display "[object Object]" as seen in the linked screenshot.