When using the Report Explorer, the tree automatically expands to all levels expanded, on making any change to a Property for the currently selected item.
This makes using the Report Explorer very frustrating, so you end up shouting at the window to 'Stand Still!".

The ReportFooter does not print at the bottom of the last page if that page doesn't contain data, even with PrintAtBottom=true set. Can this feature be changes to always print the ReportFooter at the bottom of every page?

Add a property to be able to suppress duplicate values in a column, which could be  optionally shown after a page break.

Why is it that the telerik report designer is locked down and cannot be used as a set of controls in a custom application as any other telerik control. We would like to use the report designer controls in an application we make to give it our look and feel and so we can give it the functionality we require. Why limit your customers by locking down your report designer. One of the great things about telerik is a great set of products and customer support. If we had a way to get at the Telerik.ReportDesigner.Core.dll we can figure our where the controls are and display them in our app. I don't understand the marketing behind the locked down report designer. How does it benefit your customers? You can still have a locked down designer for those customers that don't want to customize it. Providing access to Telerik.Reporting.Core.dll will give your customers the ability to customize the report designer to their needs. Telerik sells controls that customers use to make applications that they sell, so whats the difference with the designer? 

The Reporting Map control is orientated with North at the top and South at the bottom.
I would like to display the map in a report with a different orientation, similar to the Rotatable Maps view displayed at google maps here: https://maps.googleblog.com/2010/02/introducing-google-maps-labs-your.html

The Silverlight report viewer control never clears the cache out of the database. Steps to reproduce:

1. Configure the database cache provider with mssql as defined in the documentation.

2. View a report by setting the Report property of the viewer with the class name of the report.

3. Clear the report when the user is done viewing the report by setting the Report property of the viewer to null.

I see the request to invalidate the report session, but the cached data remains in the database. 

Raw request:
 <s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"><s:Body><RenderAndCache xmlns="Telerik.ReportService"><format></format><report></report><deviceInfo xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" xmlns:i="http://www.w3.org/2001/XMLSchema-instance"><d4p1:KeyValueOfstringanyType><d4p1:Key>InvalidSessions</d4p1:Key><d4p1:Value xmlns:d6p1="http://www.w3.org/2001/XMLSchema" i:type="d6p1:string">["035e4409-655c-49ab-a5b0-b9bf5e0d9859"]</d4p1:Value></d4p1:KeyValueOfstringanyType></deviceInfo><parameters xmlns:d4p1="http://schemas.microsoft.com/2003/10/Serialization/Arrays" i:nil="true" xmlns:i="http://www.w3.org/2001/XMLSchema-instance" /></RenderAndCache></s:Body></s:Envelope>

I am using Barcode = Code 39 for some labels and the ratio i get is 2.0. Is there a way to increase and arrive to 2.5 or 2.6?

Would it be possible to prioritize which characters can "Break" when wrapping text inside a text box?  For example "foobar/foobar" will not break at the slash, it'll instead break at the character that hits the width limit. It would be my suggestion that punctuation be prioritized for "breaking" before all other characters, in the event that there is no space.

In the attached example, the column headers are dynamic (localized), and there's no way to predict what the text will look like (in whatever language)... Though I accept that no matter what, a string longer than the textbox width will need to break somewhere, I'd prefer that you break on "better" characters if they are present.

(Pretty nitpicky, I know, but this would save me trying to code the logic into an expression or function... which could prove complicated due to variable width of fonts)

We redefining an existing table style (ie. Aspect) in an external style sheet, the user should be able to select the style like now, but disable the style generation in the report file.
Currently, we need to go in the designer.cs file to remove all unwanted styles.

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.

This is your reply to one of our questions regarding RTL support of crosstab component.
"The Crosstab item will not change its layout (does not support RTL layout flow). You will have to create to separate reports with similar layouts. One report can be used with RTL languages, and another with LTR languages.
Note that row groups can be added only on the left side of the Crosstab item. "
SO our request is to fully supports RTL.

Self referencing parent-child hierarchies (i.e. Manager-Employee) are a common structure, They should be supported in your grouping mechanisms. 

Currently this is only possible thru a workaround as in http://www.telerik.com/forums/cross-tab-report-with-a-self-referencing-hierarchy#7p4BaddGV0iam8J6bT_dpQ

I believe an enterprise reporting tool should support this out of the box.

Thanks,
Henry

Graph should be binded to a single DataModel, but many Graph properties should be then be binded to a specific property of this DataModel:
-each series should be binded to a specific property (which would be a list). These properties would be the data.
-general Graph items like axis title should also be able to be binded to other properties, to allow more complex use. These properties would be the metadata.

As it is now, all the data are put in a single list (not developer friendly at all), and using metadata is impossible.

Currently, the designer automatically increase the width of parent containers when a control is moved or resize and goes outside the current parent size.

But this can be problematic with bad paging in some cases. 
As the automatic grow may be needed, I propose to increase the parent size with a settable minimal step:

When having set everything to have a width of 160 mm, just moving some controls can currently increase slightly the size (like 160.23 mm). But if the report has a minimal grow step of say 5 mm, in this case it will be resized to 165 mm, a visible size difference (therefore, layout can be corrected when the grow was unwanted).

Add a way to force a Page Break in a Multi-Column Report, as opposed to producing a 'Column Break'.
These are 2 separate concepts of a Column Break and a Page Break.

A report viewer feature for SSRS (RDL) so that we can utilize the SSRS 2016 HTML5 in our apps

It will be nice to have a proper (Official) TypeScript definition for the HTML5 Report Viewer. 

Reporting webapi to support asp.net core