For now, Telerik Reporting is supporting SQL Server data provider only. Once the .NET Standard  2.1 Is live, please include the support for multiple data providers.

I want to define conditional formatting on table row, after I define a filter and save it, I can not save the conditional formating dialog, it gives exception.

What am I doing wrong?

 

When you have some <br /> tags in the HTML, the behavior is different between Kendo Editor and Telerik Reporting.

I attached HtmlTextBox result and Kendo Editor behavior. 

in the real world, an exception can really occurs in the resolve method, and I want bubble this unknown exception coming from resolve method and not a custom exception written in GetParameters method

The ExportDialog window in Windows Forms Report Viewer does not respect resource files for localization and displays always the default text.

The Fonts meta information in the PDF rendered document is incorrectly populated. It contains entries for missing Font subfamilies, i.e not available during report rendering. We observed this with Franklin Gothic Medium Condensed font that has only Regular subfamily.

I am currently using the Telerik Reporting 13.0.19.222 software to generate an annual report that we will send to our constituents. I can render the report to a multi-page PDF for emailing and local archiving with no PDF standard or PDF/A-3b just fine. However, we intend to send the rendered PDF reports out to be printed and mailed by a publishing company that has requested that the documents comply with the PDF/VT standard.

Is this something that is being considered and/or implemented in a future release?

Thank you in advance,

Grant Hoelscher

The rotated text using Times New Roman font appears truncated in the Html5 Report Viewers. The text is properly rendered in formats other that Html.

If the command for fetching Report Parameter AvailableVlues times out, the WPF Viewer freezes with hidden parameters' area, i.e. it is not possible to enter other values and the application needs to be restarted.

It would be great if all the localizable/localized strings/resources can be exported, e.g. into an Excel file, so they can be given to a translator and imported once translated

I would like WPF viewer to behave like WinForms viewer and to keep the content of the rendered in XAML report in the page area in case of exceptions when exporting in other formats.

When attempting to export a report in Excel 97-2003 format, an exception is thrown: 

"The type initializer for Telerik.Reporting.Excel 97.Workbook threw an exception. Object contains non-primitive or non-blittable data."

As HTML, PDF and OpenXML-based renderings are supported on Linux/macOS machines, please remove the old Excel 97-2003 format.

Hi Team,

 

As Heat maps are not supported by Telerik reporting, Could you please let me know if you have workaround solution readily as a demo . If not please suggest the which third part libraries to be used in C# solution.

While a project is being debugged, VS crashes when the report's zoom is changed in the VS Designer. Please, check the attached screenshot.

Drilling from one report to another using dates prior to 1970 do not work and end up getting "parsed" as null. That works correctly for dates greater than or equal to 01/01/1970, since that's the epoch for Unix time, but fails for dates before that.

The text of vertical textbox is cropped and duplicated on the next page in crosstab

 For example in WinForms, it is initialized and ready for setting different device settings.

The expression parser throws an exception when parsing an expression that calls .ToString() method after closing parenthesis like the one below:

=(Fields.Value1+Fields.Value2).ToString()

If the two operands in parentheses are converted to double, the expression is parsed and evaluated correctly:

=CDbl(Fields.Value1+Fields.Value2).ToString()

 

After R1 2019 Telerik Web Report Viewers use Kendo splitter for resizing Parameters and Document map areas. At this point, there is no way to change the Parameters Areas position.

The MS Access OLE DB provider is not providing the correct QuotePrefix, QuoteSuffix, QuoteAlias that is causing errors in the SQL Query Designer that is part of the Standalone Report Designer.