As a reports author, I would like to reuse one and the same page section in multiple reports, so that I can modify the header at once and spare the copy/paste operation.

As a developer integrating TRDX/TRDP reports into my app, I would like to have built-in functionality to pass runtime data sources corresponding to the data sources defined at design-time along with the ReportSource, so that I can feed the report with custom data easily instead of having to deserialize the report and traverse all DataItem-s

It would be nice if the parameter window to enter Report parameters in  preview mode would remember the last values entered between invocations.

When configuring a datasource through the wizard, the 'Select Statement' TextBox should standard support keyboard shortcut ctr+A to selelct all. Having to open the context menu is a bit awkward.

When selecting several items, it should be possible to change the size and location of all of them, at least if the values are the same

When you have your .trdx and external stylesheet files in a separate directory (e. g. a server directory available to all workplaces) it gets very difficult to show the .trdx files in ReportViewer without manipulating the reports a lot by code.

1. The external stylesheets are searched in the bin\Debug directory of the main application when using Kind="Relative".
2. What is even more annoying is the fact that all SUBREPORTS are also searched in the bin\Debug of the main application. I have to recursively look through all report items if there is a subreport and set its location.

It would be very nice if the ReportViewer supports some kind of "path-to-reports" property and locate all the dependend files like subreport or stylesheet in this directory.

At present one cannot have a subreport in report header/footer. This is such a limitation 
e.g. you have a company header which you want in every report. Normally what you expect is to make a subreport and include that in header of other reports. So if you change any details you can edit that subreport and it get reflected in all other reports. But unfortunately you have to include the company header in every report not only the controls but also in the datasource.
I used to develop in MS Access back in 90s and even then its reporting has this feature as standard.
So come on Telerik 

Create your own parameter syntex, and translate it to the database specific one according to the provider name.
For example, MsSql uses "@" character while Oracle uses ":" to identify parameters.
We need to be able to execute the same report against multi database types.

Currently the list of marker is limited, but it isn't the case for the WPF RadChartView.
RadChartView permits the display of specifics points (like a vertical line for displaying a limit), but it isn't possible in report.
WPF DataTemplate would surely impossible to reuse in report, but some other custome template should be available like SVG, bitmap, or UTF-8 character (not the best customable solution, but it already increase a lot the possibilities)

Ability to make a column in table or crosstab having width based on its content

When converting Crystal Report templates (rpt files) to Telerik Reporter templates it would be very helpful to include the schema settings in the associated ttx file which provides the dataset info. This allows the layout to map properly to the converted template. Also any imbedded SQL statements found in the Crystal template could be captured and the conversion wizard could then query the developer on database connection requirements. These two abilities would make conversion a complete tool allowing rapid deployment of new Telerik report templates.

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

The date format of the report parameters is related to the culture, but the data source parameter is not.

The Upgrade Wizard should show information about the important changes from the old version up to the current one. I.e, if the client upgrades from R1 2016 to R3 2017, the wizard should aggregate and show all the important changes between these versions.

Need a way to export a drill down report with the visibility toggles as they are set in the Reportviewer.

Currently, if row visibility is something other than the default, if you export a report using the suggessted method:

Dim result As Telerik.Reporting.Processing.RenderingResult = _
		reportProcessor.RenderReport("PDF", ReportViewer2.ReportSource, New Hashtable())

Using fs As New System.IO.FileStream(filenamePDF, System.IO.FileMode.Create)
    fs.Write(result.DocumentBytes, 0, result.DocumentBytes.Length)
End Using
 
It loses the user defined visibility and exports the default.

If you use the Reportviewer.ExportReport() call, the report retains it's visibility, HOWEVER it prompts a file save dialogue. Unfortunately we cannot allow file browsing for our clients.

If we simply had an option with ReportViewer.ExportReport() to specify the file path to save to (preventing the file dialogue from popping up), this would be a non-issue.

I've been using the Stand Alone Report Designer a fair bit lately but find myself having to switch between the Home, Insert and Data tabs quite a bit. It would be a great time saver if the Report Designer had a dockable toolbar (defaulted to the right) like in Visual Studio with short-cuts to adding things like Text boxes, pictures, etc.

Regards

Edu

It's confusing which rule does what by looking at the current UI...would be nice to give them aliases\friendly names which mean something when you go back 2 months later, know what I mean?

It would be a great help to have a feature that can copy a whole Column in a crosstab to another one.

As opposed to having to iterate through every entity in a report using send to front/back, how about just creating the PDF in the order in which the entities exist on the report? Ignore the order in which the entities were created - export them in the order they appear

On the design surface, there is no indication of the z-order of the sibling items nor an easy visual way to change it. Please improve this.