Need to support installing and running reporting server restful API from within linux.

Ability to localize Standalone Report Designer created reports without the need of using custom functions.

I had a very challenging time getting Telerik Reports to work with my business objects. I'm not the only one -- see this thread:

http://www.telerik.com/forums/how-to-use-object-data-source-in-report-designer

This could be improved by:
1. Don't make users manually edit <Telerik.Reporting>. Create a UI in the designer where DLL's can be manually selected.
2. If there are errors loading the DLL's in <Telerik.Reporting>, tell the user, rather than failing silently, which is the current behavior. Importing reports from DLL's has the same silent-failure behavior: if there's something not quite right about the DLL's (wrong architecture setting, for example), you just see "no reports to import" rather than the actual error (bad file format, or whatever).

I think a little work on the user experience around custom business objects would make new users who want to use the stand alone report designer in this way much happier. I was really surprised and frustrated that a modern product would fail like this with no exposed error messages.

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

Some reports contain a lot of detail (audit reports, sales reports).  Users need to quickly find transaction numbers, etc. when balancing financials.  

Can the Telerik Reporting libraries be available for install as a NuGet package that can be hosted on a local NuGet server?

Hosting on the public NuGet server would be even better, but I would imagine that would be harder to get approved.

Hello,
RadPdfProcessing supports PDF/A 1-3 since Q1/2015. It would be nice if the Report engine would also support PDF/A exports.
PDF/A will bevome the future european standard for invoicing (ZUGFeRD) and is the current  standard for long time archival of digital documents.

Regards,
Chris

Currently, if you wish to hide extra details on the second page of a report, the space taken up by the area is left blank which looks terrible and not conducive to professional report design.  

Related threads:


http://www.telerik.com/forums/different-page-header-on-first-page

http://www.telerik.com/forums/hiding-the-page-footer-leaves-a-blank-space-in-the-report

Unfortunately using report books for this is not a valid option.  Using the Report Book means quite a bit of extra work when all you need is for the second page to not have an glaring empty space.  If I understand the process correctly, this means creating 2 reports which are nearly duplicates plus merging with Report Book for each 1 report that you are developing.  This is unresonable to expect from enterprise shops that will develop hundreds of reports.

I urge you to review your implementation in order to find a way to implement this feature in the future. 

if you can provide a default resource file of report designer, and provide the same name convention rule of the resource file, then we can translate it by ourselves.

Please provide the possibility to localize the HTML5 Report Viewer UI in a way that doesn't require modifying the template.

It's already possible to localize the messages shown by the HTML5 Report Viewer as shown here: http://www.telerik.com/help/reporting/html5-report-viewer-localization.html
Something similar for the actual UI would be great.

Allowing custom actions would greatly increase the power and flexibility of reports and the report viewer.  While the current set of actions provide great functionality, they are still somewhat limited in scope.  If actions were able to handle their own execution instead of having the individual report viewer implementations handle their execution, customers could enhance the functionality as they see fit.

Hi,

 

Can you create a nuget package for the Telerik.ReportViewer.Wpf.Themes.dll.

 

 

 

Thanks

Marc 

This is your reply to one of our questions regarding RTL support of crosstab component.
"The Crosstab item will not change its layout (does not support RTL layout flow). You will have to create to separate reports with similar layouts. One report can be used with RTL languages, and another with LTR languages.
Note that row groups can be added only on the left side of the Crosstab item. "
SO our request is to fully supports RTL.

Add Right to left attribute to the three levels of the reports, with default 'inherited' of child levels:
Level 1: The report document
Level 2: Report Section
Level 3: All type of object and controls including Table/CrossTable

add the possibility of show the parameters area on right/left/below of report viewer.

The PDF rendering does not respect the new line characters in a multiline text watermarks, rendering it on a single line.

My Scatter Chart  has 3 points that are very close and I want to change label alignment for 1 as Top, 2 as Left and 3 as right.

Currently, there is no option to automatically place the labels so that they don't overlap.

I have a customer request to Scale to Fit One page when exporting a report to excel. It is a large document created via the crosstab. I am Requesting that on export to excel, the property of Scale to Fit page can be set.

In some cases, the data source might have dynamic columns meaning that the columns might change for different report runs. I need to be able to detect if a particular column is available using an expression so that I can handle its absence without showing an error to the end user.

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.