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..
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.
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 the possibility of show the parameters area on right/left/below of report viewer.
Please provide an option to launch a sub report directly from within the main report designer (standalone version). Example, in Crystal reports, if there is a sub report within a report, a user can double click that sub report and it opens it as a new report tab. This is very convenient rather then having to chase down the path to the subreport and open it manually.
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.
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.
While configuring the WebServiceDataSource with the wizard if an error occurs on the Preview page, show the setup request details.
During runtime show the request details in the application trace.
It would be really useful if EntityDataSouce was updated to support Entity Framework Core contexts. EF Core depends on Standard 2.0 so can run on .NET Core or the full framework.
On export to MS Word, a numbered list that spans two pages restarts at (1) on the second page. Instead, the numbered list should continue numbering from the first page.
For example, if a list has five items and the fourth item starts on a new page, when I export the report to MS Word, the first three items are numbered (1), (2), and (3), and the last two items are numbered (1) and (2) again. The last two items should be numbered (4) and (5).
In addition, if an item in a numbered list splits between two pages, the item is numbered twice: once at the beginning of the item and again on the first line that appears on the next page. The line at the top of the second page is numbered (1). This second number should not appear.
The attached file shows both these issues.
It's currently not possible to define in the HTML5 Report Viewer "per Report" the available Export formats. It's also not possible to alter the List in the given JS Events because the List of PDF,XLS,etc is loaded on MouseOver in the menu. Would be great to have some kind of options, array list in the widget options to define what export formats are displayed. Kind regards, Otto.
Loading huge DB schemas in bulk is time-consuming. Add lazy schema loader for the table column definitions in order to improve the user experience when using DB with a huge schema.