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.

Is it possible to do the conditional formatting of a text watermark? For example, I am checking if the parameter value is equal to Passed, then font color of watermark should turn green else it turns red.

When dynamically create a new tab which contains a report viewer, only the first report is rendered correctly. The subsequent tabs with report viewers are empty.

Telerik saving to PDF issue intermittently.  The issue is that the graph gets skewed and then won’t open in Acrobat once the report is exported.

It would be extremely useful to have a Crosstab export the entire hierarchy as groups in Excel. SQL Reporting Services does this when exporting a report created there. I realize that this would mean generating the entire dataset prior to the export in order to expand all the data, but as I said, SSRS does this without a noticeable performance delay.

 

 

Currently to add a new Shared/Project DataSource a new component item is added and then modified manually to Telerik Reporting DataSource. This is not obvious and is kind of peculiar workflow. Thus consider adding ItemTemplates to manage the process for adding new Telerik Reporting Shared/Project DataSources.

After the report is translated we started to change the sequence of parameters. This works fine except the translated texts do not move with it. So parameters have the wrong text.

When a TextBox is deleted from a localized report, if a new TextBox is added, its localized value would be set to the localized value of the deleted TextBox.

When a column is hidden through binding, a small gap appears to the border of the next column.

Asking to enable typing into the font combo box in standalone Telerik Report Designer.

 

The concept would be to click on the font drop down and just start to type the name of the font and have the list shift to that position for you.

Please add to the Telerik reporting step line chart the same functionality that exists in the kendo ui step line chart.   There is an attribute for justified = true that allows the line to step directly to the marker rather than having them placed in the middle of the step.  Please see the attached images for the current result vs the desired result.

I used https://docs.telerik.com/reporting/html5-report-viewer-howto-use-it-with-reportserver to setup an HTML5 Report Viewer with Report Server. After running the project, the viewer does not load. It seems that it could not find telerikReportViewer script. 

Workaround: Instead of

<script src="/api/reports/resources/js/telerikReportViewer"></script>

use absolute path:<script src="http://yourreportserverhost:83/api/reports/resources/js/telerikReportViewer"></script>

Please put the tool windows in a Docking system, like Teleriks.  Forcing the property window to be pinned to the right side is a UI/UX issue. Studies have shown that placing it on the left, makes it easy to use since the object your assign property value is very close and the distance the mouse must be moved it greatly shortened.

Hi,

It's very frustrating having to type in Style Names in the Properties tool window.

All styles names both internal and external should be known by the standalone designer or Visual Studio designer.

This would be a big productivity boost.

Karl