Telerik.ReportViewer.Mvc.SendEmail class in Telerik Reporting ASP.NET MVC does not contain fields "Cc", "Subject", "Body" (https://docs.telerik.com/reporting/t-telerik-reportviewer-mvc-sendemail)

But JS documentation dontains such fields (https://docs.telerik.com/reporting/html5-report-viewer-jquery-fn-telerik-reportviewer#sendEmailOption).

I'm using the latest version of kendo ui and telerik reporting.

In general, the Page sections do not collapse or expand based on their content. Also the report header and group header sections span the width of the column.

It would be nice if, for example, have another section that either could expand/collapse based on the content and do not be affected by the report's page settings.

When opening the Edit Expression dialog, the state between HTML view and Design view is lost when using build-in functions, but it keeps the value if it is a simple text with formatting.

At the moment it's only possible to have your reports in old-fashioned projects.

It should be possible to add/design reports to SDK-style projects. That should work no matter what target framework is (.NET Core, .NET Standard or .NET Framework).

I would like to formally request the ability to "sign" in some fashion a trdp/trdx file.  Note that if only the new file format is supported then that would be acceptable.

Basically, I would like to apply some signature that we could, if we so chose, read from the report file to verify that it was us that created or last modified the file.

If we need to use a separate tool to apply the signature other than the report designer, that would not be an issue.

The signature could be anything that Telerik/Progress decides we can use such as a code signing certificate, a strong name, etc.

Using the last modified time, or a hash value created from the current contents of the report file would not be a good solution as that would mean we would need to have a list of the hash values for each report and it would need to be updated every time the report is changed.
We are looking for something that could be applied to all reports that we create and that clients could not replicate.

This would need to be something that clients who we deploy the report files to cannot replicate and therefore if they modify the report file using the Telerik designer, it would remove that signature.  This way we can easily programmatically determine if the client has modified the report, and therefore prevent using it as if it is ours.

Note that we provide the ability to use custom reports in our application which are treated as separate from our core provided reports.  Also, I had posted to the forum asking if this is currently possible (https://www.telerik.com/forums/sign-telerik-reports).

Thank you.

Telerik.Reporting.OpenXmlRendering.2.7.2.dll from the latest release (R1 2009) references the from version of DocumentFormat.OpenXml. See the screenshot:

Here the screenshot for the prev version (R3 2018 SP2):

Because of this our projects referencing DocumentFormat.OpenXml 2.8.1 (the latest version) are all broken. Xlsx rendering simply does not work anymore.

If I have a dropdown or multi select list as a report parameter, if there are many items in the list then you are forever scrolling. Can a search feature be built in so that you can search for items you want in the list and select rather than having to scrolling up and down?

I need to contract the services of a developer that is really good at Telerik Reporting - I am having an extremely hard time finding such a person - can you help?

It would be nice if we can set ToolTips for the report parameters in design time

With the recent release of StackExchange.Redis v2.0 there are HARD BREAK changes. I would like Telerik Reporting to work also with this version.

As for now, from the supported rendering extensions, only the PDF renders a document map as Bookmarks pane. All other rendering extensions ignore document maps.

It would be nice to have Document Map in Word documents too.

When I export a report to MS Word that includes a bullet list and one of the items in the list spans two pages, the item gets two bullets in MS Word: one on the first line of the bullet, which is correct, and on the first line of the bullet that appears on the next page. This second bullet should not appear. The attached screen shot shows what I mean.

On export to MS Word, a numbered list that spans two pages restarts at (1) on the second page. Instead, the numbered list should continue numbering from the first page. 

For example, if a list has five items and the fourth item starts on a new page, when I export the report to MS Word, the first three items are numbered (1), (2), and (3), and the last two items are numbered (1) and (2) again.  The last two items should be numbered (4) and (5).

In addition, if an item in a numbered list splits between two pages, the item is numbered twice: once at the beginning of the item and again on the first line that appears on the next page. The line at the top of the second page is numbered (1). This second number should not appear.

The attached file shows both these issues.

It will be good to have a section similar to Page Header/Footer that can be placed on the left/right of each Page.

Currently the query builder (in the Report Designer) cannot automatically build queries if there are multiple separate relationships connecting two tables.

Here's an example:

Table A: Orders

• OrderID
• ShippingAddressID (FK => AddressID)
• BillingAddressID (FK => AddressID)
• ...

Table B: Addresses

• AddressID
• AddressLine1
• ...

If both tables are selected in the query builder, you will get the following columns:

• OrderID
• ShippingAddressID
• BillingAddressID
• AddressID
• AddressLine1
• ...

In other words, only one copy of the address data is pulled in, despite the two separate FK relationships. I would expect something like the following:

• OrderID
• ShippingAddressID
• BillingAddressID
• ShippingAddressID_AddressID
• ShippingAddressID_AddressLine1
• BillingAddressID_AddressID
• BillingAddressID_AddressLine1
• ...

We ran into this issue because we are using Telerik Reports to provide reporting for a data warehouse, and we have multiple relationships in our "table A" pointing to a date dimension (our "table B"). The current workaround for this is to write your own SQL queries instead of relying on the query builder, but we would like for our business users to be able to create reports on their own, and they don't know SQL.

Allow the WPF viewer theme to be set using resources for the current window instead of setting resources on application level. Now the theme can be set using <Window, but this approach will not work for the Search window, which is a separate window and therefore fails to resolve its styles.

Using the send e-mail functionality, in CC field the emails are not received.

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.

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.

Several community members asked about a Report Viewer suitable for Vue.js applications.

We will appreciate your feedback in this feature request. You can leave a comment with details about functionality requirements for a Vue.js Report Viewer e.g. initial setup, updates of the displayed report and ways of passing report parameters' values.

Thank you.