We have developed additional logic around the Telerik Reporting Engine so I don't know if this would be valuable to anyone else or not but I would love to have the ability to associate custom properties to a control.  

The use case that comes to mind most is the logic we have implemented to auto size text that displays on a report to fit in the area provided.  We use a control naming scheme to determine what controls should be auto sized and how they should be sized in relation to other parts of the report.  It is typically assigned used with a Panel, a TextBox, or an HTMLTextBox.

I would love to have the ability to add two associate two additional properties to these controls that could be used in the stand alone designer to allow users to set an AutoSize (true / false) and a SizingGroup (string) property on these controls rather than worry about making sure the control is named properly.  I would allow users to more easily leverage this functionality.

I realize that it is unlikely that this will be implemented since it wouldn't be widely used but I like to dream.

At runtime there is no way to easily access values from fields within the same row of a report using the WPF ReportViewer.  We have a requirement for our application where users may double-click a field and trigger the applicable editor to appear for quick access.  To enable this functionality, we need to retrieve values from within the same row as the field that was clicked.
While the TextBlock that was clicked may be accessed, there is no way to easily determine which controls within the control hierarchy belong to the same row as all page content is lumped into one canvas.  Searching for values by Name is not possible either as the name is not passed into the generated controls.
It is also not possible to create custom IAction implementations to handle this functionality either as they are not supported.

It would be nice to have 3D chart capabilities such as those found in the WPF ChartView or even the KendoUI charts.  The Telerik Reporting charts , although feature rich, are rather plain looking.

In general I quite like the Stand Alone Report Designer but one thing that is a bit painful is that the default height of new fields are way to big. About half the current height would be more appropriate. It wastes time to have to resize every field after adding it, and especially also having to also shrink the height of details section is you added a new field to it.
It would be ideal if you could add a configuration section where everyone can specify their own default values such as field height but page size would also be handy.

Thanks for a very handy product.

Regards

Edu

Please add support for PrivateFontCollection.  When the program is deployed to a location where it does not and cannot install system level fonts (for various reasons), it makes an application built with Telerik Reporting volatile.  

I submitted a ticket due to a conflict we ran into.  Telerik's  response was to install the fonts on the system.  However, the system controllers response is "this it why PrivateFontCollection was invented...you have the control to use any fonts you want."  As a result, a developer has to either give up Telerik (ex. for DevExpress which supports it) or change the deployment entirely which seems utterly ridiculous.  Due to some project constraints, we changed deployments in hopes of it being rectified.

This should also be supported in the standalone designer. 
There is currently a workaround via external assembly but this is not very elegant.

I'm not a PDF expert, but if something can be done in a free library, a pay'd version of reporting tools should do it also right.

In many cases, I do a report to PDF for my clients. Since PDF contains useful data, I't normal to assume, client will use copy-paste and copying data to Word, Browser, etc.

Similar approach was used, when I created a project for the General prosecution of SR, but there the PDF was generated by PdfSharp and by writing text-outputs (with esired font, size, etc.). The result was correct.

Unfortunatelly with Telerik it's not so. I've tryed to explain it in a ticket, but I only got excuses, explanation about lignatures and so. I got/left myself almost convinced, but my main point is the starting sentence in this description.

The original issue: http://www.telerik.com/account/support-tickets/view-ticket.aspx?threadid=893196

It would be useful to have tooltips to table header columns so we can explain what each column is showing.

Like the NeedDataSource, it will be nice if there was a PreRender event or similar.
So that way I could programmatically adjust elements based on the report parameters. Example: a column selection parameter (dropdown) that would then in the 'PreRender' remove or hide the columns from a table if the column name isn't in that multivalue parameter.

When a date is set as a report parameter in the HTML5 viewer, it formats the parameter as a JSON date using a timezone.  Where no time is specified this results in a time part added to the date when received at the server.  This is a problem, especially for browser in a negative offset zone, e.g. US, where upon the date goes to the previous day.  Please add support for parameter types of date, where no time is present and no conversion is done anywhere.

This is not a clone. It's a new request I had to add, since the old was closed with a technically fault answer. By technically fault I mean possible, but in real scenario unusuable.

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. So I'd like to see such a possibility in telerik reports.

The suggested solution - with the bindings http://www.telerik.com/forums/how-to-bind-the-datasource-of-a-subreport-in-the-designer is technically wrong. It assumes that the child report knows at which level he resides inside the main report. The child report (or it's binding) should have not such info embedded. Let's see on an example. Let's have a dataset:
User.Address
User.PostalAddress
User.Wife.Address
User.Wife.PostalAddress

The dataset should be bound to the main report. The main report should have 2 sub-reports (address and postal addres). It can have an another sub-report (for wife data) which then would again have 2 sub-reports inside for addresses.

Using the technically wrong solution, the addresses for the main user should have a binding expr. like: =ReportItem.Parent.DataObject.xy and the wife's addresses have like: =ReportItem.Parent.Parent.DataObject.xy

There is a big problems with such a binding: the child must know the hierarchy of the data.

The technically clean solution is to have a dataset assigned to the main report. When adding a sub-report to the main report, via binding we should set the new data-source for the sub report. something like: MainReport.Data = dataSource. SubReportAddress = dataSourceOfTheCurrentReport.Address. SubReportWife = dataSourceOfTheCurrentReport.Wife and inside "wife report" the next sub-report for address address should have a binding again like: SubReportWifesAddress = dataSourceOfTheCurrentReport.Address

In the Configure Object Data Source Wizard, add a method of filtering the displayed Business Objects.
Where a large number of Business are display, scrolling can be painful to find the required one.

Reporting webapi to support asp.net core

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).

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?

just the same like here
https://www.combit.net/en/reporting-tool/pdf-object/

Add a Property for all controls to be able to set whether the control appears on every page of the report. At present the entire Group Header/Footer may be set to appear on every page, but not just a single control.

We required a Barcode and ID. No. to be displayed on every page of the report. It has been really complicated to utilise a series of Group Headers and Sub-Reports to achieve something that should have really easy. The layout of the Report could not be modified as it is set by Government.

Telerik Reporting should facilitate turning the complex into the straight forward.

I find it extremely limiting and frustrating to not have control over how the .NET Report class is initialized, and not being able to pass in any type of object/dependency (either into the constructor or by setting a property.) This makes it very difficult to keep custom reports decoupled from other code modules and make them unit-testable. 

There is the InstanceReportSource, which would have been perfect to solve this problem, but it's apparently deprecated.
http://docs.telerik.com/reporting/t-telerik-reporting-instancereportsource

DevExpress reports for example allow you to create the report instance yourself, and you can pass any objects you want directly into the constructor. 

This is what I find to be the biggest drawback to Telerik reports. 

Currently, adding Sparklines (http://docs.telerik.com/reporting/sparklinesanddatabars#sparklines) or Data bars to the report requires manual formatting of the Graph item (hiding the Axes, Labels etc.).

Let us know if you think the built-in support for this type of chart would be useful when creating reports. Please share your ideas/thoughts in the comments and give a vote for this feature to support it.

An example of Sparklines/Data Bars is provided in our online demos - http://demos.telerik.com/reporting/product-sales?&skinName=silver(Product Sales report).

Thank you.