Ideally, if the user prints a report, the output should be the same as what they see on the screen.

Currently, if the user prints/exports the report sometime after previewing it, the data will be updated and they will not get what they see.

The following Base64 image:

iVBORw0KGgoAAAANSUhEUgAAATIAAABaCAYAAAA7FtpGAAAABHNCSVQICAgIfAhkiAAAAZ1JREFUeJzt1EkOgkAAAEHw/3/Gk9HoIEsksZOqm8wCDtrzNE3L9GJZnh/nef649j62Zu+a0bzR/Me80bWttXuf6ej3PHNWZ85y7V6j8T17nd3v6LtaG79q3mj+0fdy9Pz2/g/OzLvqHLf2+MUZfPutbN1j6/2N1t6+PyrA/xMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMgTMiBPyIA8IQPyhAzIEzIgT8iAPCED8oQMyBMyIE/IgDwhA/KEDMi7AzLSZLNf8xCVAAAAAElFTkSuQmCC

is recognized by the Reporting engine as SVG, which results in the following error in the PictureBox:

An exception has occurred while processing 'pictureBox1' item:
System.Xml.XmlException: The '�' character, hexadecimal value 0xFFFD, cannot be included in a name. Line 1, position 5.
   at System.Xml.XmlTextReaderImpl.Throw(Exception e)
   at System.Xml.XmlTextReaderImpl.ParseElement()
   at System.Xml.XmlTextReaderImpl.ParseDocumentContent()
   at System.Xml.XmlLoader.Load(XmlDocument doc, XmlReader reader, Boolean preserveWhitespace)
   at System.Xml.XmlDocument.Load(XmlReader reader)
   at System.Xml.XmlDocument.LoadXml(String xml)
   at Telerik.Reporting.Svg.RadSvgImage.SvgDocumentFromXml(String xml)
   at Telerik.Reporting.Processing.Imaging.SvgImageItem.CreateImageInfo()
   at Telerik.Reporting.Processing.Imaging.IImageInfoMapExtensions.StoreImageData(IImageInfoMap imageInfoMap, IImageItem imageItem, ICache cache)
   at Telerik.Reporting.Processing.PictureBox.ResolveImage(Object value)
   at Telerik.Reporting.Processing.PictureBox.ProcessItem()
   at Telerik.Reporting.Processing.ReportItemBase.ProcessElement()
   at Telerik.Reporting.Processing.ProcessingElement.Process(IDataMember dataContext)

As explained in this support ticket (https://www.telerik.com/forums/specify-default-print-settings---number-of-copies), our customers want to be able to set the default value of the number of copies for a report since they require multiple copies for their business processes.

Would it be possible to enable setting the default values for the printing when a report is generated?

When a TRDP/TRDX report is imported to a CS report, the produced .designer.cs does not have Unicode encoding, instead, it is with ANSI encoding.

Because of this, some of the report text might instead be displayed as ????

The workaround is to Save As the file, from Visual Studio, with Encoding which will open a window where you may change the encoding to Unicode.

I have a multipage report and my Html5 Viewer is set up in an ASP.NET Core application in .NET 5. The viewer's settings are:

viewMode: "PRINT_PREVIEW",
scaleMode: "FIT_PAGE_WIDTH",
pageMode: "CONTINUOUS_SCROLL",

The problem is that I cannot scroll down to the end of the report.

The issue may not occur in other frameworks with the same report.

in the new/current Version "16.2.22.914", when dragging an DataSource-Field on the Report, the resolved expression is wrong.

In the previous Version "16.2.22.622", this worked as expected, see Screenshot.

The attached report demonstrates the issue.

Currently a single instance of the WPF Report Viewer will often use multiple different HttpClient instances to talk to the Report Server.  This means that cookies added as part of earlier requests may not be sent in later requests.  If the Report Server is behind a load balancer that uses cookies to implement 'sticky sessions', this loose behavior with cookies will cause requests to get routed to different servers which is not ideal.  It is possible to use a storage mechanism on the server that natively supports a web farm (such as the Redis storage option) but that can be tricky to set up.  

Instead, if the report viewer were to re-use the same HttpClient instance for all requests (including initial render request, export requests, print requests, etc.), the load balancer could work to route all requests to the same web server and then any storage mechanism (such as the simple File storage option) would work.

This issue was reported back in 2017 and I'm running into the problem again in 2022.  See: https://www.telerik.com/forums/wpf-reportviewer-cookie-behavior

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.

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.

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.

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

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.

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.

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?

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. 

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.

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.