If the controls and PDF generated from Designer or API from scratch will be 508 compliant? PDF needs to be tagged, so when a reader reads its images have text alternative for it to read.

HTML content is currently displayed verbatim in Report Viewer Tooltips. Tooltips should work as kendo tooltips usually do, rendering HTML when detected.

Please add full support for asp.net Core. What you currently have is not nearly complete. We need to be able to use the report designer and add reports in a .net core project and we need to be able to use reports that have objectdatasources. Currently object datasource does not work with .net core dll's.

I would like the end user to be able to resize the DocumentMap and if possible the Parameters Area.
Many times when the names are long they are cut off.
Many of my user will have clients will have similar names like law firms with a particular attorney name appended.

Example:
LAW FIRM OF DOUCHE AND BAG - JAMES SMITH ESQ
LAW FIRM OF DOUCHE AND BAG - KIM JONES

With the current implementation it would be cut off before you could see the end of the name.
LAW FIRM OF DOUCHE AN
LAW FIRM OF DOUCHE AN

This requires them to use the scroll bar back and forth instead of resizing the area like the old webforms viewer.
Please see picture for references.
Also if there was an option for the names to have tooltips so they could just hover that would be helpful.

The parameter map at least will wrap the names that are long it’s the DocumentMap that is the bigger problem.
Thanks John

We need ein new Function in the group "Aggregates" to insert a "SubTotal". It means a function like "Sum(expression)", but it provides not the sum of the whole group, rather the Sum of des Group until this Page. It is normaly printes on the pageFooter-Section or groupFooter-Section. But it would be nice to have this Sum on the next Page of the groupHeader.

In the "Configure SQL Data Source" window. Let us be able to maximise the window for the "Select Statement". First, the query builder can do nothing as soon we use a little bit complexe query. And for long query, it's a pin in the ass to work with two scroll bars. 

Thanks

Add support for WKT - POINT and LINESTRING formats in shapeMapSeries to display point and line objects on the map. Our team works closely in the road industry, where there are many point and line objects that need to be displayed on the map. These objects can have aggregated data, which can be displayed in different color and type of lines. In addition, such point objects as road signs would be good to be able to display in the form of well-known notations from pictures that are pulled dynamically.
See also http://www.telerik.com/forums/objects-on-map#kClfHLNy5kWfh44rXndNcQ

The images rendered by the XAML rendering extensions are using Linear scaling mode for fastest processing. This method decreases the quality of the rendered image, when image scaling occurs. The preferred scaling mode should be set through extension's Device Information Settings.

It would be nice to catch the parameters of the HTML5 viewer and the report engine.
I need to encrypt the parameter Ids that is visible to any man-in-the-middle attacks.

I did encrypt the parameters, and tried to use "CustomReportResolver : IReportResolver" to catch and decrypt it before send to the report engine or the report data source. But the resolver has only the report Id or name.

I'm using UriReportSource because we need to evaluate and try dynamic reports.

Diagram attached. 

When there are sub reports and KeepTogether would require a dataset to use multiple pages the report renderer fails to honor page breaks. Rather than use the new page it should be using to present the page, it bleeds onto the prior page which has a page break set. 

See Ticket #1144729 for all the relevant information regarding the version, setup etc. and attached examples. I was directed here to the feedback portal so your staff has led me to believe this is an existing issue with the current iterations of the report project.

Additionally me original forum post below.
https://www.telerik.com/forums/keeptogether-not-honoring-page-breaks 

It would be nice to have an option on the report book to Collate and set a Multi-Value Parameter or Data field as the list for collation. Essentially if i have 3 reports (A, B & C) and they have parameters of Start Date, End Date and Client(Multi-Value) and i want to collate by selected clients. The report book should then render the report as follows

Report A - Client 1
Report B - Client 1
Report C - Client 1
...
Report A - Client 2
Report B - Client 2
Report C - Client 2
...
Report A - Client 3
Report B - Client 3
Report C - Client 3

Collation is a very common scenario when working with multiple reports

Add support for reusable items. Create a report item like Panel, Table or Graph and then export and share to other reports. If a reusable item is modified a change can be propagated to all reports that use this reusable item.

When we do a copy/cut and paste operation of controls (textbox, htmltextbox, etc.), paste the controls at the mouse position. 
Thanks

One of the main features the clients require when exporting the reports to XLS or XLSX is to have the page width already set to 1 page. But for none of these exporting options, this is possible, unless you intercept somehow the export functionality prior to rendering the document to the client

Actually multi value parameters is not supported on WebServices source. Multi value are passed as [string1,string2] instead of $paramName=string1&paramName=string2.

Multi value has to be passed on query string on correct way!

Add the new Crystal theme to the theme ResourceDictionaries available for the WPF and Silverlight ReportViewers. 

When a report with a document map is reloaded due to parameter change, the currently selected position in document map tree is lost and the current page number is reset to 1. Preserving the page number does not make sense, because changing a parameter may change the rendered pages count, hence there is no guarantee that the same page number will correspond to the previously examined page.

However, the viewer can persist the currently selected items hierarchy in the document map tree and try to select the same nodes after the report is reloaded. This would be particularly useful in Report Book scenarios where the book will navigate to the same report once the parameters are changed.

Steps to reproduce the problem:

1. Open the Report Book demo.

2. Navigate to Dashboard report by clicking the third item in the Document Map pane.

3. Change a report parameter, i.e. select 2002 in the Year parameter editor.

4. The viewer reloads the report book and navigates to its first page, clearing the highlighted items in Document Map pane.

Export options can be limited through the application configuration file, where the settings will be applied to all viewers and for all reports. For more info: Limit export options in ReportViewer to certain format only.

It would be nice to have specific export options per report without the need of building custom UI to handle the export.

While configuring the WebServiceDataSource with the wizard if an error occurs on the Preview page, show the setup request details.

During runtime show the request details in the application trace.