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 '184.108.40.206' of package 'Telerik.Reporting'.
https://api.nuget.org/v3/index.json: Package 'Telerik.Reporting.220.127.116.11' is not found on source 'https://api.nuget.org/v3/index.json'.
Unable to find version '18.104.22.168' of package 'Telerik.Reporting.Services.WebApi'.
https://api.nuget.org/v3/index.json: Package 'Telerik.Reporting.Services.WebApi.22.214.171.124' is not found on source 'https://api.nuget.org/v3/index.json'.)
Packages failed to restore
Please help this is urgent .
The Telerik Reporting only support fixed size page now. But sometimes we need continues-roll paper mode.(like: receipt paper) Some reporter tools: ActiveReports, it has 3 mode:(Page Reports, RDL Reports, Section Reports) On "Telerik Forums / Reporting Forum" there is already some people asked it before 2 years ago. But until now the basic feature not release....
The problem is not getting the error via Dot Net programming, but the complete layout destruction of the report as a result of the fact that a picture (in our case a thumbnail of a provider) is unavailable. Catching the report error is not an option. It is too complicated and even if we succeed in obtaining the error, it will be very complicated to remove the unavailable url on the fly and re-render the report again. This seems to be a "known issue" for about 8 years! My question: Is it possible to keep the remaining report "intact" if such an error occurs? This shouldn't be too difficult for the development team..
First, we need the ability to have the controls in a Page Header Band to Grow/Shrink based on their contents. Second, the Page Header Band also needs the ability to Grow/Shrink based the first Condition and any other Conditional Formatting settings of controls with in that band. This is request becuase of the design of the Report Header Band and how it is designed for Multi Column Reports. The Report Header Band does all what I am asking for, however, in a Multi Column Report, it's only the size of the column width, which is a problem for some of our reports. We need it to be the entire page width. Some suggests to create PAGE BOOKS seems a bit complicated to do for such a simple request. I have been using different report writes in my 25+ years of programming, and Telerik Reports is the first one that I have used, that has these limitations..
Add progress bar that indicates when the report would be fully rendered.
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.
We display data inside an HtmlTextBox that was entered using the RadEditor. It would be great if the Reporting HtmlTextBox could be brought much closer or even in line with tag support as the editor. We are frequently running into issues with uncommon tags (that we strip out for the HtmlTextBox) and also with spacing being different. We work around the issues we have, but continuing increased tag support or auto stripping of unsupported tags would be very appreciated.
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.
There is the newly introduced WebServiceDataSource which enables me to get JSON data from a web service. I'd like to be able to use JSON as a data source for a report without using a web service. For example, the JSON might be embedded inside the report definition, or it might be coming from an external text file (URI or URL), or even pass it programmatically to the report at run-time.
Ability to localize Standalone Report Designer created reports without the need of using custom functions.
All Telerik Reporting assemblies to be distributed via Nuget packages, in order to ease deploying a solution that uses Telerik Reporting and to share the solution with other developers. Note: Without having Telerik Reporting installed on the machine, there will be no design-time support (Upgrade and other wizards, VS Report Designer, etc.). The purpose of the packages is only deployment.
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.
Some reports contain a lot of detail (audit reports, sales reports). Users need to quickly find transaction numbers, etc. when balancing financials.