I hope the user can edit or save or load the report template in winform application like devexpress.

Good afternoon. When I export a report with a crosstab that contains vertical titles to PowerPoint, the titles are not visible. Please could you help me fix it. Thank you.

The rotated text using Times New Roman font appears truncated in the Html5 Report Viewers. The text is properly rendered in formats other that Html.

It would be nice to have a report viewer component that does not rely on the full .net framework as described here.  https://docs.telerik.com/reporting/html5-report-viewer-asp-net-core-2.  I have a project that is not built against the full framework and would like to integrate reporting without converting all of my projects.

I have tried like operation in condition formatting and it is not working.

Much like the way Excel has the ability to utilize VBA functions. it would be usefull and more conventient for developer if they could include custom functionality/functions in a report rather than use an external assembly.  The steps involved to include/use an external assembly is daunting at best and not at all straight forward.  

Something like you right click the report and one of the menu options is "Add Custom Function".  Or in the expressions dialog box have an option to create/add a custom function.  

You get the point.  I'm sure your team of developers could come up with something. 

The Fonts meta information in the PDF rendered document is incorrectly populated. It contains entries for missing Font subfamilies, i.e not available during report rendering. We observed this with Franklin Gothic Medium Condensed font that has only Regular subfamily.

The ExportDialog window in Windows Forms Report Viewer does not respect resource files for localization and displays always the default text.

Hi

 

I am no longer able to build my reporting project on TFS on line, (I used to be able to) I get the build error

The nuget command failed with exit code(1) and error(Errors in packages.config projects
    Unable to find version '13.0.19.116' of package 'Telerik.Reporting'.
      https://api.nuget.org/v3/index.json: Package 'Telerik.Reporting.13.0.19.116' is not found on source 'https://api.nuget.org/v3/index.json'.
    Unable to find version '13.0.19.116' of package 'Telerik.Reporting.Services.WebApi'.
      https://api.nuget.org/v3/index.json: Package 'Telerik.Reporting.Services.WebApi.13.0.19.116' is not found on source 'https://api.nuget.org/v3/index.json'.)
Packages failed to restore

 

Please help this is urgent .

 

regards Laz

After setting the Margins under the Page Settings, the Width should be automatically set.
The Width should be the Paper Width with the Left and Right Margins subtracted.
What happens when this 'formula' is not used, which one takes precedence?

It would also be nice to display the Height as a read only property.

Support generating reports on .NET Core running on a non-Windows platform, esp. macOS or Linux-like OS.

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.

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.