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.

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. 

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?

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.

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.

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

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.

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.

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:

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.

Currently, the fields' names are case-sensitive for those 2 data sources while other data sources, like the CSV for example, will ignore the casing.

For example, if there is a JsonDataSource with a Column1 field, it has to be written exactly as is in the expression while in the CsvDataSource, the field will be resolved even when written like Fields.column1 in an expression.

Product: Telerik ReportServer 8.1.22.622 ( 2022 R2 SP1 )

I can't delete any report file (.trdp) after being uploaded to Telerik Reports Server (Web Management).

When I click delete an error message says 'An error occurred when trying to delete report, can't connect to agent service'
but the reports agent is running well and other commands like (upload report, rename) also work fine except for Delete.

So I had to delete the reports server's storage folder (~\Data), setup everything again and re-upload all my reports again each time I want to delete a report.

If you would please fix this critical problem in the next versions so I can use Telerik Reports Server again.

Please fix it ASAP. Thanks

• The Report Viewer component is not correctly creating DateTime type fields. It renders them of type textbox.
  The current version of the Telerik Reporting library is: 16.2.22.914.
  We use Telerik UI for Blazor 3.6.1.
  We are using the Telerik.ReportViewer.Blazor library

On the last step of the SqlDataSource Wizard in the Web Report Designer, executing the query to preview the records displays the columns with a lowercase character at the beginning which can be confusing.

After the wizard, the names of the columns are correct and can be used as expected by the designer.