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.
Diagram attached. When there are sub reports and KeepTogether would require a dataset to use multiple pages the report renderer fails to honor page breaks. Rather than use the new page it should be using to present the page, it bleeds onto the prior page which has a page break set. See Ticket #1144729 for all the relevant information regarding the version, setup etc. and attached examples. I was directed here to the feedback portal so your staff has led me to believe this is an existing issue with the current iterations of the report project. Additionally me original forum post below. https://www.telerik.com/forums/keeptogether-not-honoring-page-breaks
I have a requirement to implement multiple report with same content except the table content. Table content is binded through List(by ID, fetch details from table). Can you please guide me, what should be my approach?
When selecting report in print preview mode with a windows DP setting of 125% the report is not corrected. This results in report which is shifted on paper when printing is invoked. See attached file. Request a setting which can overrule the operating system DPI setting.
freeze certain columns in a table when we scroll right and left in Telerik Report and the same should be applicable when we do export to excel
Our client is strongly requesting a "zoom" by graphical selection feature, as available in their former tool qlikview (or amcharts, for example). I am surprised this feature has not been requested yet, since any user would greatly benefit from it. It's an extremely powerful and intuitive way of restricting your selection of report input parameters in a visual manner. By drawing a rectangular selection with mouse over the graph, you restrict the range of both x and y axis to the selected ranges, allowing quick zoom to the area of interest Examples: just draw selection rectangles on a chart in one of the examples below https://www.amcharts.com/demos/scatter-chart/ http://us-b.demo.qlik.com/QvAJAXZfc/opendoc.htm?document=qvdocs%2FSocial%20Media%20Buzz.qvw&host=demo11&anonymous=true
Would it be possible to prioritize which characters can "Break" when wrapping text inside a text box? For example "foobar/foobar" will not break at the slash, it'll instead break at the character that hits the width limit. It would be my suggestion that punctuation be prioritized for "breaking" before all other characters, in the event that there is no space. In the attached example, the column headers are dynamic (localized), and there's no way to predict what the text will look like (in whatever language)... Though I accept that no matter what, a string longer than the textbox width will need to break somewhere, I'd prefer that you break on "better" characters if they are present. (Pretty nitpicky, I know, but this would save me trying to code the logic into an expression or function... which could prove complicated due to variable width of fonts)
Add the ability to control the relative position of text in relation to the image for both Radio & Check Boxes, such as TextImageRelation property used on your WinForms Radio & Check Boxes. This would allow the following options: Overlay, ImageAboveText, TextAboveImage, ImageBeforeText, & TextBeforeImage.
At present one cannot have a subreport in report header/footer. This is such a limitation e.g. you have a company header which you want in every report. Normally what you expect is to make a subreport and include that in header of other reports. So if you change any details you can edit that subreport and it get reflected in all other reports. But unfortunately you have to include the company header in every report not only the controls but also in the datasource. I used to develop in MS Access back in 90s and even then its reporting has this feature as standard. So come on Telerik
I have encountered this problem numerous times but I will list one of them. When printing a weekly schedule in the format of a calendar, the days of the week print top to bottom when the desired layout should be L to R. We have resorted to various hacks to get this to work, but this is another feature of ***(which we are converting from) that is not supported in Telerik Reporting. It would be nice if there was an OPTION to flow L to R as opposed to Top to Bottom.
Create your own parameter syntex, and translate it to the database specific one according to the provider name. For example, MsSql uses "@" character while Oracle uses ":" to identify parameters. We need to be able to execute the same report against multi database types.
Currently the list of marker is limited, but it isn't the case for the WPF RadChartView. RadChartView permits the display of specifics points (like a vertical line for displaying a limit), but it isn't possible in report. WPF DataTemplate would surely impossible to reuse in report, but some other custome template should be available like SVG, bitmap, or UTF-8 character (not the best customable solution, but it already increase a lot the possibilities)
As opposed to having to iterate through every entity in a report using send to front/back, how about just creating the PDF in the order in which the entities exist on the report? Ignore the order in which the entities were created - export them in the order they appear
Interactive Action events are triggered when a report is in preview and the user moves over an item with configured action. Actions are triggered by click, that cannot be replaced with other key combination. It is be more useful if there is an option to set the key combination or other interaction that should trigger the action.