Background:
I create an ASP.NET Web Application - Empty. I add to it a Telerik HTML Report Viewer page. The wizard creates a new REST service with a sample report. Inside the Html5ReportViewer.html file is the line
<!--If Kendo is used it should be added before the report viewer.-->
<script src="/api/reports/resources/js/telerikReportViewer-15.0.21.326.min.js/"></script>
with a trailing / in the src attribute. This works perfectly.
Problem:
I have a ASP.NET Webforms website that displays reports from the Reporting web application. Pages that display a report also have this script tag. However, any time there is an update for the Reporting toolkit, if I use the Reporting Upgrade Wizard, (Visual Studio 2019 "Extensions" menu -> Telerik -> Reporting -> Upgrade Wizard) the script tags get updated with the latest version, but the trailing / in the src attribute is no longer there and the page breaks because the Javascript library is not loaded. Adding in the / fixes the problem. Is this intended behavior or a bug in the upgrade wizard?
1. Open report in the EUD.
2. Click "Export Template".
3. Select the open report and click "Next" and "Finish" to complete the wizard. The newly created template is visible in the User Templates as expected.
4. Click "Export Template".
5. Select the open report and click "Next" and "Finish" to complete the wizard. Warning is shown that this template exists. https://gyazo.com/91cac78640a551411c67df4abaecce78
6. Click "Yes" so that the template is replaced.
Internal Server Error. The operation was canceled is thrown in the viewert when the SVG contains
<?xml version="1.0" encoding="UTF-8"?>We pass Report Parameters as Strings and later convert them to Floats in the Report. This works fine on our production systems in Switzerland but fails on dev machines that use different system locales.
Hello,
I am receiving the TypeError: $kendoHtmlEncode error in an Angular Report Viewer with the SystemJS. I am also using a .NET Framework (4.6.2) WebApi based Reporting REST Service. See the following screenshot of the error.
Additionally, the Report Viewer UI is loading until the error is thrown and the report never loads as shown in the following screenshot.
Note that I am also using a separate process for running each project.
For additional reference, I have attached a sample that reproduces the error. See the following steps to run the sample locally.
Please let me know if you need any additional information. Thank you.
Dear Telerik,
We use Azure App Services to host the reporting engine API.
Azure App Services validate all incoming requests to ensure they come in with valid Bearer JWT tokens. Your suggested workaround of validating the tokens only on some requests in the application would require us to turn off built-in Azure validation, which elevates security risks.
Can you please ensure [authenticationToken] is added to ALL requests from the Angular tr-viewer to the API, not just some requests?
Please redesign the viewer to authenticate all its requests to the backend service. Including but not limited to the requests report viewer makes to download generated report documents as attachments by performing get document requests through window.open() or any other methods.
We appreciate your efforts to obfuscate such requests; however, these efforts need to be in addition and not instead of industry standard security practices.
Thank you very much,
Sergey Nosov
Sr. Integrator/Developer,
Calpine Energy Solutions
Not sure if you are aware of this but the new property SkipBlankPages in 2021/R1 will result in a corrupt (unopenable) PDF/XLS if the report contains no data.
The output used to be a blank report.
This behaviour is fixed by setting the Value to 'False' but this now requires the developer to remember to set this value on each new report. Perhaps the default should have stayed as 'False' and those who wish to remove blank pages could set it to true.
We are aware the property is set to true by default.
We have now had to modify (and subsequently retest) > 100 reports.
The generator should probably not create a 'corrupt' file in these cases.
Kind regards
When a textbox cannot fit on the current page and its Style.VerticalAlign is not set to Top, the textbox is pushed to the next page, although its KeepTogether property is set to false and its Value is null or empty.
This scenario usually happens when a textbox in a table grows vertically because the table contents also grow - it might be another nested table or any other data item. The solution is to either set the visibility of the textbox to false or set its Style.VerticalAlign to Top.
Currently, when using the Search widget in the WPF Report Preview the results highlight all of the text in the textbox that holds the matching search text. Although helpful, in cases where there is a long block of text it is less so.
It would be even more helpful if the search results highlighted only the text being searched, as can be seen in other apps, like browsers and document viewers.
The attached picture shows the current search widget, the interaction with the results and a report, and my requested change.
When you change a parameter, the parameter controls will be disabled while it fetches the data and then enabled again when the data returns, which is correct.
If you have a parameter with AvailableValues, the parameters will be disabled while it fetches the data but then never get enabled if the report has no data. You have to click the refresh or back button to enable them again.
Figure 1 report is generated using the data source in figure 2. Data in column "Value2" is mapped to the column Text in the generated report.
In the below-generated report, text in row one "Default CUS for CDV" is truncated. A feature to make the user know there is more data to be shown will be great.
Figure 1
Figure 2
So, Adding an option to display an indicator such as “...” for truncated strings so that the viewers get to know there is more information to be displayed
Or
Provide an option to absolute break (display until last possible character) of the string rather than word-wrapping if there’s more content than the text box width.