If you add two Bindings for the same property in the designer when you click OK, an error "Index must be within the bounds of the List. Parameter name: index" occurs and the Bindings are ignored.
We use WebServiceDataSource with OData query in our reports. Sometimes OData can through an exception.
In our case, we have added Web Service DataSource and set this OData query for its Service Url:
If you see the query, it is selecting "ProductName1" property of "Product #1". But "ProductName1" property does not exist (correct property name is "ProductName"). When we use Postman for the OData query above, it shows an error which you can see from attached picture (ErrorWhenWeUsePostman.PNG, "Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'"). From the second picture (TelerikReportingGeneralError.PNG, "An error has occurred... Response status code does not indicate success: 400 (Bad Request).") you can see the result of our test report (in html5 report viewer) that has the same OData query.
The question is when we preview our report (in html5 report viewer) how can we show the error message that OData sent instead of showing Telerik reporting general error?
Instead of this message:
An error has occurred while processing Report 'TestReportWithWebServiceDataSource': Response status code does not indicate success: 400 (Bad Request).
This OData error message should be handled and shown on browser (html5 report viewer) when previewing report:
Could not find a property named 'ProductName1' on type 'NorthwindModel.Product'
FYI: We are using Telerik Reporting version 188.8.131.52.
This is my post on Telerik forum related with this: How to get internal error message from Custom Report Resolver
I have a JsonDataSource that contains a Base64 string field I want to use in a PictureBox.
When I drag the field from the Data Explorer in the Report Designer, it creates a TextBox with the text content. When I run the report, there is an error "A generic error occurred in GDI+'.
Consider creating PictureBox when dragging a Base64 string instead of TextBox.
There is a common error message received often after upgrading Telerik Reporting:
Unable to get report parameters. An error has occurred. Cannot read a document with the specified schema: http://schemas.telerik.com/reporting/2023/1.1. You might be using an older version of the product.
Obviously, I have a mismatch between the new report that I created and the deployed Reporting application. To create the report that is generating this error, I copied from an existing (and working) report. Only changed the Stored Proc being called and a few field names. Everything else is the same.
Except -- (OBVIOUSLY) -- when I saved the report -- the Designer changed the schema version.
You need a way in the DESIGNER to display the schema version of the report. If these reports are TRDP then I don't see an obvious way of viewing the schema version of the report. I opened both reports in the designer and tried to find a way to view the schema versions of a working versus non-working report. So that, I could determine which version of the designer that I need to drop back to (in order to create my copy of an existing report).
In your error message, you could easily provide additional detail but do not. You just say "product". Obviously, you know this but you don't report it to user. For example, you could say -- "This report has schema version xx.xxx.xx but the Reporting Engine can only run reports of schema version yy.yyy.yy and below" or something to that affect. Good error messages would go a long way to avoiding this frustration.
I need to know when one of my users has canceled the rendering of the report in order to update the UI accordingly.
Please consider firing a 'renderingCanceled' event when the above occurs or passing an additional parameter to the updateUi event to specify the rendering state.
If the CanGrow property of a TextBox/HtmlTextBox is set to True and Left and Right Anchoring is applied, the Height of the text box will be determined based on its design-time Width.
Thus, even if the actual final Width of the item is enough to fit its contents on a single row, the text box can have a larger than necessary Height.
React Report Viewer throws error ts(7016) on importing it in a TypeScript project:
Could not find a declaration file for module '@progress/telerik-react-report-viewer/dist/cjs/main'. 'C:/Users/dnikolov/Desktop/ReactTypesScript/my-app/node_modules/@progress/telerik-react-report-viewer/dist/cjs/main.js' implicitly has an 'any' type. Try `npm i --save-dev @types/progress__telerik-react-report-viewer` if it exists or add a new declaration (.d.ts) file containing `declare module '@progress/telerik-react-report-viewer/dist/cjs/main';`
When designing reports with lots of parameters (which is very common for my usage), I often get error message "Missing or invalid parameter value" or "Syntax error in expression". I find it very time consuming and annoying to manually check "all" parameters in order to identify which one is causing the issue.
Would it be possible to include more details in these error messages, e.g. by including the name of the (first) incorrect parameter? Preferably for the message in report viewer / preview, but at least in the log file.
While some viewer options such as the pageMode, viewMode, etc. are already exposed and configurable through code, the parameters are not. This means that the viewer will always load the report with the default report parameter values which can troublesome.
For example, I need to be able to pass a JWT to a WebServiceDataSource inside my report and I use a report parameter for doing so. This works as expected when I use a simple report viewer but when the report is loaded by the Web Report Designer, it is not possible to pass a value from the front end where the designer is initialized.
When rendering a report with a Graph on Linux, the labels of the Graph are not aligned properly.
For example, right-aligned labels are offset to the left depending on the content and length of each label.
I apply the operator TOP N (=5) to get only the first 5 records of a dataset sorted by a DateTime field. It sorts the data correctly as seen in the previewed report, but still returns all data records rather than the first 5 of them.
If I apply the TOP % operator, the dataset seems filtered as expected.
The workaround I have found is to apply second TOP N filtering with an empty expression as seen in the linked screenshot.
I have attached also a sample report demonstrating the issue and the workaround.
Error: Unable to cast object of type 'Telerik.Reporting.Processing.Expressions.ProcessingEvalProvider' to type 'Telerik.Reporting.Expression.IValueObject'
is thrown on previewing the data source results in the WebServiceDataSource when the Runtime or Design time expressions are left completely empty or the runtime value is a report parameter with an empty Value property.
What's the long-term plan for supporting Linux and Telerik Reporting? The dotnet design team is looking to remove support for System.Drawing.Common on Linux platforms. They're recommending compiler warnings in .Net 6, and full PlatformNotSupportedExceptions in .Net7
designs/system-drawing-win-only.md at main · dotnet/designs (github.com)
Breaking change: System.Drawing.Common only supported on Windows - .NET | Microsoft Docs
Currently the behavior of the Web Designer and Standalone Designer is different in regard to DateTime Report Parameters and its "Kind" property.
The Web Designer will assume the value is of Kind "Utc" and the Standalone Designer uses "Unspecified".
This recently became more of an issue since the newer PostgreSQL Provider versions are a lot more strict regarding the "Kind" property:
Npgsql: Timestamp rationalization and improvements
The consequence of this is not being able to use Sql parameters which will work in both the WebDesigner/WebViewer and the StandaloneDesigner:
To resolve this issue right now, one would need to resort to ugly workarounds:
To properly address this issue it needs to be possible to set the Kind property in the Viewer. Or at least the behavior between the WebDesigner and Standalone Designer should be the same.
Additionally/Alternativly it should be possible to set the target Kind in the Report Parameter.
With kind regards,