Please consider adding a standard HTML5 viewer template that does not rely on things like Font-Awesome which is neither standard, nor adheres to any sort of disability compliancy (note: Font-Awesome Icons can not be read by screen readers, for the visually impaired). A better option would be to use Scalar Vector Graphics for the icons. It makes little sense to offer a single, non-standard, HTML5 template, out of the box... which forces the end developers to standardize it before it can even be used.

F.e Jasper's SubReports have a property called DataSource. The sub-reporst uses this dataSOurce for rendering it content. The DataSource is always set on the Main report. Everything via designer, no need for coding.

When I have a coded dataset (in NeedsDataSource) the designer has no concept of the dataset.  I would like to somewhere define the properties that would be available myself so I can use them from the explorer and in the expression editor...instead of having to keep going back to the codebehind to find the property names.

I have attached reports in PDF and excel format. When we export a report to excel file, the resulting excel file has extra empty rows as you can see in the attached excel file. Rows 10, 12, 15, 17, etc are extra rows. Can those rows be automatically removed and rows with data automatically expand?

When providing custom UI in the ASP report viewer (may also include other viewers) to facilitate the selection of report parameter values, it would be useful to be able to get the available values.  Currently only the definition of available values can be read from a report, there is no mechanism to actually get them without reading that definition and generating your own SQL query etc from the SQLDataSource.

Resolving the values ourselves is dangerous, from a data integrity point of view.  We are re-writing the mechanism to get the values which may not fully reflect the report designer’s intention as we may miss duplicating all of the functionality the report engine does when it processes available values.

The reason why this would be useful is that the current report parameter UI supplied by the viewer is extremely basic and limited.  For example, sometimes we may want to select values from a tree view.  We may wish resolve them through a series of wizard steps.  Either way, being limited to the basic UI doesn’t fit well with individual solutions.

I base this request on the currently available functionality in Microsoft’s reporting service.  This does currently have a function we can call for the reasons described above. 

The attach example Test.html does not work against my service. When monitored in Fiddler I cannot see the parameters being passed on to the call? Not sure what I'm missing this was taken from online API example.

I used trial version of Telerik Designer for SSAS report creations . Database connection is working fine , however when report results were displayed in preview mode , then for each record in query results additional page will be added . I used tables and charts to show results , the results are the same.  Is it special feature of trial version or just a program error?

When exporting a report in the format supported by the viewer, allow the user to open in addition to saving. Now they must save and then open and allowing the open option would be more efficient for the view of the report

The standalone designer throws an error, e.g. "Missing operator before", if you make a mistake in the conditionalFormatting expression and close the expression editor.  You are then unable to correct the mistake without opening the trdx in a text editor.  Please change the behaviour so that the editor can still be opened even if the expression has syntax errors.

Add support for the <pre> tag.  This would allow content to be added to the HtmlTextBox without having to worry about encoding it properly.  We use the HtmlTextBox frequently in situations where we want to apply mixed formatting.  

This would help in several scenarios.  One scenario that came up recently was when I wanted to render literal space.  I got around this by replacing every other space with a non-breaking space but the pre tag could have made this much easier.  Other situations involve getting text from the database that could include a < or > symbol which we have also got around making sure we run the text through an HtmlEncode routine.

When I select a column in a Crosstab and set a Binding for a Property (for example Visible) it will overwrite all existing Bindings for all Textboxes in that column without any warning. This shouldn't happen. At least there should be a Message that you overwirte existing Bindings and ask if you really want to do that.

Graph markers, it would be nice to have a few more marker types for the chart, I would really like a up and down arrow, or a reversed triangle. also a left and right arrow/ triangle, and how about a star?

Please add ability to show vertical line markers on a Line series graph as show in attached file.

Having a white background in a view when using the dark theme is very bad for the eyes.
You should check all your UI in Visual Studio, as I already asked in the past for a correct context menu for dark theme (now done).

Looks like if print in windows service will be has some problem , because print in windows service can't display the print dialog.

The order of the items in the Border Style Properties should be changed such that Solid is the second item in the list, after None, as this is the most frequent option. This would allow the Border Style to be changed to Solid with a double-click.

Add the functionality of the Page Up/Down as well as Home and End to the WPF Viewer Control, so that the displayed page may be controlled using the keyboard.
These buttons should also work with the CTRL+ variations.

I am using Telerik Reporting with MVC 5, and would like the ability to use the custom parameterEditor with MVC. If anything, I'd like to be able to create it with razor MVC, and then use jquery to add the parameterEditor.

Currently, the size and location of items displayed in Properties view are rounded value, but the real value written in the .Designer.cs isn't rounded at all.

This created some imprecision in size and location, possibly resulting in unwanted resizing of the report width, or in overlap.
Now, it is only possible to correct this in .Designer.cs, and the user don't see the problem without zooming at maximum or opening the .Designer.cs

Rounded value seems better than some unneeded decimal, but then the value displayed should also be written in the .Designer.cs