On vertical axis, the title is always rotated at 90°. When using short title like "Y" this become very strange, we must be able to set its rotation like the labels.

Loading one simple report with one user can spike the cpu.  Multiple users on that same report cause the cpu to go insane.

Global caching needs to be a thing in reporting...you guys are always looking for performance improvements anyway.

Current Scenario as defined by support:
- Person 1 hits report 1, reporting processes\renders it
- Person 2 hits report 1 (same params), reporting processes\renders it
- Person 3 hits report 1 (same params), reporting processes\renders it
...

Expected Scenario:
- Person 1 hits report 1, reporting processes\renders it, processed data result is cached
- Person 2 hits report 1 (same params), reporting retrieves the processed data from cache, and report is rendered
- Person 3 hits report 1 (same params), reporting retrieves the processed data from cache, and report is rendered
- Person 4 hits report 1 (same params), reporting retrieves the processed data from cache, and report is rendered
(10 minutes elapses, or whatever the timeout is)
- Person 5 hits report 1, reporting processes\renders it, processed data result is cached

Change Currentpage, TotalPages, DocumentMap properties to Dependency Property... to enable DataBinding... 

Adding support for label connectors. This little line that attach the label to his part in the chart like the ones from Kendo UI: http://demos.telerik.com/kendo-ui/pie-charts/index

Please add support for the text-indent attribute.
HTMLTextbox used to support the css attribute text-indent, but the support was removed a couple years ago.  If used alone, it still appears to work on report, but then when used in combination with other css attributes (specifically the new justification alignment), it does not work as it should.

This support would help with normal formatting items that come up when entering a paragraph that should start out indented but wanted to be justified as well.  Attached is a test report showing it not working when combined with justification, but then working when it is alone.

having the htmlTextBox in the report viewer is a big help when it comes to multi-formatted text, however, we also want those formatting to be applied when the user exports the report to excel worksheet instead of just plain text like what's happening now.  It's tedious breaking block of text into table cells just to apply individual formatting for each part.

Add the ability to either specify the number of Columns in a Table during creation or allow a entered number of Columns to be added after creation.
Both would be my favored solution.
Creating a Table with numerous Columns is tedious when you have to add one at a time.

The ability to add these types of images to reports would be incredible. We deal with numerous companies in the manufacturing sector. These customers have drawings that they would like to print along with their reports (think of a production order to build something, we show a list of the materials to use and the drawing/cad would be required).

Are there any plans to standardize the shortcut keys in the Report Designer? There are many places where CTRL+C, CTRL+X, CTRL+V, ESC, DEL do not affect the field in focus, but instead a parent window or out-of-context control.

For example:
1. Open the Edit Parameters dialog for the Report Source dialog (In my example, I chose a URL/File and clicked Edit Parameters)
Drop down a parameter name, and hit Escape. Escape is the standard key to close a drop-down. In this case, the "Cancel" button on the dialog is triggered instead. This causes changes to be lost in the dialog.

There are a pile of examples; there's a dialog where pressing delete key does not delete the contents of a field in the dialog, but instead deletes the (selected) field from the report itself; but they don't come to mind right now as I haven't run into them lately.

These 2 functions will allow special actions to be applied to the first and/or last pages, such as displaying "Continued..." in a Group Footer Section, on all but the last page.
These functions must be available in all sections of the Report. Currently the PageNumber and PageCount Properties are only available in the Page Header or Page Footer Sections. Therefore they cannot be used with Bindings or Conditional Formatting in the Detail Section, Group Header Section or Group Footer Section.

After setting the Margins under the Page Settings, the Width should be automatically set.
The Width should be the Paper Width with the Left and Right Margins subtracted.
What happens when this 'formula' is not used, which one takes precedence?

It would also be nice to display the Height as a read only property.

Several community members asked about a Report Viewer suitable for AngularJS projects. We provide the HTML5 Viewer that requires a link to jQuery on the page - http://www.telerik.com/support/code-library/html5-viewer-in-angularjs-project (HTML5 Viewer in AngularJS project).

We will appreciate your feedback if the HTML5 Viewer (Javascript widget) is suitable for your AngularJS project. If it is not, please vote for this feature request and leave a comment with details about functionality requirements for an AngularJS Report Viewer e.g. initial setup, updates of the displayed report and ways of passing report parameters' values.

Thank you.

I saw here

http://www.telerik.com/forums/tooltip-on-pie-chart

that there is no Tooltip Function for Telerik Reporting in the Line Charts right now. 

Is that still correct?

If yes please take it on your list because it is a very important Feature for my customers!

Many thanks

Markus

The problem is not getting the error via Dot Net programming, but the complete layout destruction of the report as a result of the fact that a picture (in our case a thumbnail of a provider) is unavailable. Catching the report error is not an option. It is too complicated and even if we succeed  in obtaining the error, it will be very complicated to remove the unavailable url on the fly and re-render the report again. 

This seems to be a "known issue" for about 8 years!

My question: Is it possible to keep the remaining report "intact" if such an error occurs? This shouldn't be too difficult for the development team..

Currently report parameter types are limited. We would like to pass a data table as a parameter . Tried formatting to table string outside and using HTMLTextbox, but it does not parse <table > tags. 

Currently in Telerik reporting, when we apply sorting it works on all selected columns together in a complex format. It also leads to confusion when user applies sorting on two or more columns as all of them have the sort icons. 

Single column based sorting would help end user to easily access and understand the action. In this approach user will see sort icon only on the currently selected column.

Please provide the support for single column based sorting in Telerik reporting to ease the use of sorting functionality.

Hi,

I request to support Legend of circle/line/rectangle etc. in all series so that the developer can choose the shape, as the recent trends in finance are flexibility in legend shape. Currently there is no flexibility in having circular Legend for Pie Charts. Please incorporate it in your release at the earliest.

Thanks and Regards,
Swanand

Currently, the Graph item ignores missing data points and always connects data points which have values.
According to the "Displaying Missing Values and Incomplete Periods
in Time Series" paper (https://www.perceptualedge.com/articles/visual_business_intelligence/missing_values_and_incomplete_periods_in_time_series.pdf) this approach of ignoring missing values is not recommended. The preferred approach (with gaps for missing values) is described in detail in the paper.

When using a custom IReportResolver, it gets invoked to resolve the main report but does not get called for any sub/child report. This generates inconsistent handling of the report resolve and also makes it hard to have a single repository for report templates.

request to add groups on the right side of a Table