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.

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.

Hello,

A ReportViewer control compatible with the Kendo Angular UI Framework (not the Kendo Jquery..).
When importing the css files into a project using the new Kendo angular UI framework (ngx) a lot of the components
of kendo are getting broken.

Or is there some workaround?

Best regards

Marc

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.

Reporting webapi to support asp.net core

With a complex DataModel structure, when interface is used, interface inheriting from other interface become a must.

Unfortunately, this don't work with ObjectDataSource, as it only look at its level for properties, not in parent.

Properties collecting should be done like this:


var properties = typeof(IFoo).GetProperties().Union(typeof(IFoo)                             .GetInterfaces().SelectMany(t => t.GetProperties()));

Please add support for signing PDFs with a certificate stored on a hardware token, for example on a Qualifies Signature Creation Devices (QSCD) as defined by the EU law known as EIDAS, using a native platform way (on Windows this might mean through the Certificate.msc store).

I understand that for most users, relative URLs don't make a lot of sense in reports.
However, we want export our report to PDF and link to other PDF files *in the same directory*.
As everything will be distributed as a ZIP file, we cannot know the absolute file path.
It should be easy to support this as this is supported by PDF out of the box.
Apparently, somewhere in the Reporting code, you remove URLs if they are not absolute. Just remove that check, let us put whatever we like in the hyperlinks.
Thanks.

Provide a component which wraps the HTML5 Report Viewer for use in a Vue.js application. The HTML5 Report Viewer is built using Kendo UI for JQuery components. So, one can consider the approach covered here: https://laravel-news.com/vue-wrapper-component

I'm trying to learn more about your reporting tool, but your demo only shows me a blank page. 
https://demos.telerik.com/reporting/dashboard?&skinName=default

It would be very useful to have the option of changing Sort and Toggle Visibility icons for example to a vector image. Default png is not looking good when the report is scaled or in specific styles.
Attached an example.

Currently there is no way to implement a table with html. It is pretty clear from the 1 ticket already open that this is not going to be done as it has been open for ~4 years at this point. Due to implementation challenge of the task, I suggest allowing for a HtmlTextBox to take the place of a TextBox in the table object. This will allow for better conditional formatting in a table, without having to implement the entire table function of Html.

The documentation is syntax prone to errors and does not follow well for new developers. The example code shown usually shows one step, please elaborate and show examples in depth for each topic. I have noticed in the forums that people have been complaining about errors in the documentation for more that two years and its still not fixed. I also see a lot of references to code that is shown in documentation that is obsolete or not yet implemented. The video series posted in the last few months (Q1 2015) are videos from 2009. Why?

request to add groups on the right side of a Table

Add intelligent code completion in the Report Designers Expression editor to improve the editor usability and user experience.

Add Telerik Windows Form Report Viewer configuration option to use Image rendering based on a Bitmap instead of a Metafile. This will enable the hosting of Telerik Reporting REST Service in Azure AppServices for Windows Forms Report Viewer usage.

Currently, the Graph item ignores missing data points and always connects data points which have values.
According to the "Displaying Missing Values and Incomplete Periods
in Time Series" paper (https://www.perceptualedge.com/articles/visual_business_intelligence/missing_values_and_incomplete_periods_in_time_series.pdf) this approach of ignoring missing values is not recommended. The preferred approach (with gaps for missing values) is described in detail in the paper.

This will be useful when small changes should be applied to a report based on the current rendering format. 

For example the following expression will be possible:
= "Is the document PDF: " + RenderingExtension = "PDF"

Currently, the WebSeviceDataSource is making separate request whenever data is required, consider adding a caching mechanism to reduce the number of the web requests.

Please make the text boxes in the report actually resize and grow to the correct height.  There is a catastrophic bug currently which causes the text box to stay at a single line and will not show the entire paragraph of text.

This can happen 5% of the time leading to a very unreliable framework which cannot be used in a production environment.