When a report contains data item bound to big amount of data, it takes time to export in CSV format due to data denormalization. This would be a performance improvement for big data reports.
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.
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.
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.
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.
Hi Support Team,
There an issue for exporting report to PowerPoint when there is grouping in table and tables goes to next page,
I got this error : "The given key was not present in the dictionary"
I've attached sample trdx file for your consideration.
Thanks,
Mozhgan Javadi
Using the following code for updating the ReportSource of the viewer:
ngOnInit() {
this.setParameters();
}
setParameters(): void {
this.reportViewer.setReportSource({
report: 'SampleReport.trdp',
parameters: {}
});
}
comes up with the error
Argument of type '{ report: string; }' is not assignable to parameter of type 'JSON'.
Type '{ report: string; }' is missing the following properties from type 'JSON': parse, stringify, [Symbol.toStringTag]
Currently, the workaround is to cast the reportSource object as follows:
ngAfterViewInit() {Go to page https://demos.telerik.com/reporting/product-catalog?&skinName=default
Open search dialog.
Try to move search dialog pressing left mouse button on search dialog title.
Incorrect behavior: search dialog disappears and appears again only when you finish pressing left mouse button.
When exporting a long report with ContinuousPaper = true in Word format, the output document has text cut.
Based on the limitation explained in the Pagination section in Design Considerations for Word Rendering article of our documentation, Word supports maximum page size of 22 inches wide and 22 inches high. If the page is higher than 22 inches, some data may not be displayed in Print Layout view. So, in Word, a long document couldn't be rendered.
At least, this property could be avoided when printed in Word format.