Rob Regnier

ability for report header to reclaim empty space left by conditional formatting

Currently, if you wish to hide extra details on the second page of a report, the space taken up by the area is left blank which looks terrible and not conducive to professional report design.

Related threads:


http://www.telerik.com/forums/different-page-header-on-first-page

http://www.telerik.com/forums/hiding-the-page-footer-leaves-a-blank-space-in-the-report

Unfortunately using report books for this is not a valid option. Using the Report Book means quite a bit of extra work when all you need is for the second page to not have an glaring empty space. If I understand the process correctly, this means creating 2 reports which are nearly duplicates plus merging with Report Book for each 1 report that you are developing. This is unresonable to expect from enterprise shops that will develop hundreds of reports.

I urge you to review your implementation in order to find a way to implement this feature in the future.
Feature Request by Rob Regnier Status: Completed Comments: 23 Last update: 2017-01-19T12:39:00 by Atanas Keranov
0
Pavel Tsekov

Ability to have separate page numbering in report book for individual report and one for the whole book

Using a report book with individual page numbering for each reports and a separate page numbering for all pages in the whole book. Example in attachments.
Feature Request by Pavel Tsekov Status: Completed Comments: 0 Attachments: 1 Last update: 2017-01-19T12:34:12 by Atanas Keranov
0
Markus Litters

Tooltip linechart for Telerik Reporting

I saw here

http://www.telerik.com/forums/tooltip-on-pie-chart

that there is no Tooltip Function for Telerik Reporting in the Line Charts right now.

Is that still correct?

If yes please take it on your list because it is a very important Feature for my customers!

Many thanks

Markus
Feature Request by Markus Litters Status: Completed Comments: 0 Last update: 2017-01-19T12:33:28 by Atanas Keranov
0
Ashley Harms

Do not render blank reports in reportBook

We use Telerik's report books extensively - and find that to be a very powerful way to create dynamically generated reports.

The feature request is: if a report's datasource doesn't fetch any rows don't add a blank page to the report book.

Feature Request by Ashley Harms Status: Under Review Comments: 0 Last update: 2017-01-19T12:30:19 by Atanas Keranov
0
Janosch Fricke

Add label connectors to bubble charts

Feature Request by Janosch Fricke Status: Under Review Comments: 0 Last update: 2017-01-19T12:29:03 by Atanas Keranov
0
Peter Sturgess

Add New Functions: IsFirstPage() and IsLastPage()

These 2 functions will allow special actions to be applied to the first and/or last pages, such as displaying "Continued..." in a Group Footer Section, on all but the last page.
These functions must be available in all sections of the Report. Currently the PageNumber and PageCount Properties are only available in the Page Header or Page Footer Sections. Therefore they cannot be used with Bindings or Conditional Formatting in the Detail Section, Group Header Section or Group Footer Section.
Feature Request by Peter Sturgess Status: Completed Comments: 2 Last update: 2017-01-19T12:25:26 by Atanas Keranov
0
Mamatjan Mattursun

Add more developer for Telerik Reporing team

Currently Telerik Reporting team like only a single developer hard working. So slow..... I even doubt there is no one here.
I hope hire more developer for Telerik Reporing team, and speed up.
Or maybe Telerik Company even don't care "Telerik Reporting". If that's true, please just close the project. Let us find another company request new feature and bug report who really care the customer.

Look it here. non finish request and problem already a hundred, even some request submit almost a year ago . But only 1 in development.
That's really not respect customer like us who really support The Telerik.
Feedback by Mamatjan Mattursun Status: In Development Comments: 4 Attachments: 1 Last update: 2017-01-19T12:18:56 by Pierre-Yann Bridé
0
Rusty Humfleet

Clean documentation that is well written with example code that is up to date

The documentation is syntax prone to errors and does not follow well for new developers. The example code shown usually shows one step, please elaborate and show examples in depth for each topic. I have noticed in the forums that people have been complaining about errors in the documentation for more that two years and its still not fixed. I also see a lot of references to code that is shown in documentation that is obsolete or not yet implemented. The video series posted in the last few months (Q1 2015) are videos from 2009. Why?
Feedback by Rusty Humfleet Status: In Development Comments: 1 Last update: 2017-01-19T12:10:36 by Atanas Keranov
0
John Stewart

Add ability to have group values show as 'continued' from previous page.

When groupings in a cross tab or merged row table span multiple pages the actual row label should be carried over to new page along with a label of some sort (if desired) to mark group is being continued from previous page.
Feature Request by John Stewart Status: Completed Comments: 0 Last update: 2017-01-19T12:08:56 by Atanas Keranov
0
Tom Ryan

It would be nice to have a simple built-in function to provide a page number PER GROUP.

This should also be supported in the standalone designer.
There is currently a workaround via external assembly but this is not very elegant.
Feature Request by Tom Ryan Status: Completed Comments: 1 Last update: 2017-01-19T12:07:19 by Atanas Keranov
0
Displaying items 1 - 10 of 250