I have a requirement for my report book to feature a title page and *THEN* a table of contents for the report book, followed by the report book's content. Currently, the TOC for a report book can only go at the beginning or the end of the book. My requirement required the ability to specify the TOC position more generally. Here are two possible approaches: 1. Implement the requirement as it is stated by allowing the report book's TOC to be positioned after such and such a report - the nth, or some other means of identification. 2. Honour the TOC for a report book that is nested inside another. I created a 'sub book' with the TOC as its first page and then added this an outer book. Unfortunately, the inner book's TOC was not honoured and the report was skipped. To my mind, the second suggestion above feels easier to implement (but I am guessing, of course). It certainly would allow just about any combination.
It would be good a maintain the scroll position on the parent page while navigating back from a drill-through report (using the back button of the report viewer) specially if the parent page contains a vertical scrollbar. This would enhance the user experience and eliminate the need to scroll back to the original position.
Right now, if I want a textbox to always take up space, even if visibility is set to false, I need to wrap it in a panel. I would love to be able to just check a boolean and have this done behind the scenes. Having everything wrapped in panels makes things a pain to rearrange and needlessly complex. Barring that, at the minimum, having a function to "wrap" a textbox with a panel would be nice so I don't have to create one, move the textbox, make the panel match the dimensions of the textbox, drop the textbox in, and then move the panel back where the textbox was.
Currently the images loaded in PictureBox item and Style's BackgroundImage property are rendered preserving the item's physical size. This causes scaling when the machine's DPI is different than the image DPI and affects the image quality. A specific option should allow the images to be rendered without being altered, including applying antialiasing on the target graphics object.
When printing large runs of multi page documents (production work orders where each job is 5 pages and we are printing 100 jobs), to support stapling options on the printers. All office products support this and PDF programs.
Add support for reusable items. Create a report item like Panel, Table or Graph and then export and share to other reports. If a reusable item is modified a change can be propagated to all reports that use this reusable item.
It would be nice to have an option on the report book to Collate and set a Multi-Value Parameter or Data field as the list for collation. Essentially if i have 3 reports (A, B & C) and they have parameters of Start Date, End Date and Client(Multi-Value) and i want to collate by selected clients. The report book should then render the report as follows Report A - Client 1 Report B - Client 1 Report C - Client 1 ... Report A - Client 2 Report B - Client 2 Report C - Client 2 ... Report A - Client 3 Report B - Client 3 Report C - Client 3 Collation is a very common scenario when working with multiple reports
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.
The report processor renders a report to XLSX format and adds a BOM (EF BB BF) to every embedded XML file. This is causing some open source libraries to fail to load the XLSX file, which is an issue for some of our customers. var deviceInfo = new System.Collections.Hashtable(); var reportProcessor = new Telerik.Reporting.Processing.ReportProcessor(); var result = reportProcessor.RenderReport("XLSX", instanceReportSource, deviceInfo); The work-around is to load the XLSX file in Excel (which apparently ignores the BOM) and then save it (which removes the BOM). I have read that the BOM is optional (and undesirable for compatibility) for UTF-8 encoded files, which is how the report processor renders XLSX. Please remove the BOM, or add a Device Info setting "WriteBOM = true/false", similar to the CSV export device info. Thanks, much appreciated!
As a reports user I would like more options for Line Styles in Chart plots. Currently the options are Solid, Dashed and Dotted. As a start it would be great to replicate the options in the Kendo UI Line Charts dashStyle enumeration: https://docs.telerik.com/kendo-ui/controls/charts/chart-types/line-charts#configuration-Types As the perfect option list for me: Solid ShortDash ShortDot ShortDashDot ShortDashDotDot Dot Dash LongDash DashDot LongDashDot LongDashDotDot Thanks
There is no way to fix a panel or report section so that I can print a fixed height report, internal controls of panel should grow vertically but panel it self should not grow.
Hello, today I inserted many textboxes and fields from data source and draw my own table. Problem is, if more than one field is near one positon i cant position the field exactly. If i marked more than one object i can't set x or y position per input. My idea is, mark all objects, open the position option and set for example from left 1cm, hight from the objects stays the same Thanks!
I have a report with a column that repeats values and would like to suppress the repeats. In other report writers I have worked with (SSRS, Crystal, ...) it is a right click and you select suppress duplicate values from a checkbox. The result is that duplicates on the same page are hidden, and when a new page begins the first row will show the value and then it is hidden for subsequent rows. (See attachment) I am optimistic that this functionality exists and I am simply not looking in the right place.
In some scenarios it might be useful to alter the compression of the responses returned by Reporting REST service.
Let us know if collapsing report sections in report designer would make the designing of reports more convenient for you. When reports have more complex structure with a lot of sections collapsing some of them might improve the overall design time experience.
as Microsoft is going into Power Bi it is worth to take over SQL Server Reports possible to convert to Telerik Reporting
As HtmlTextBox item supports only a limited number of HTML tags and CSS attributes, it cannot be used for rendering a richly-formatted text. The solution can be to use a WebBrowser control (https://msdn.microsoft.com/en-us/library/system.windows.forms.webbrowser.aspx) in a user function to render HTML to a bitmap and display it in a PictureBox item as described in this KB article: http://www.telerik.com/support/kb/reporting/details/how-to-render-any-html-tags-in-reports Let us know if you think providing such functionality out-of-the-box would be beneficial for your reports. Leave here a comment with your thoughts on this subject or vote for this feature.