10 Answers, 1 is accepted
Please test the latest Telerik Reporting version, where rows higher than one physical page are split, instead of having the whole row pushed on the next page - Installing Telerik Reporting. The List item and nested items KeepTogether must be set to false.
In case upgrading is not an option, the workaround is to switch back to SubReport items, where sub reports visualize data via TextBox items in their Detail section. Sub reports can be bound to the main report's data, if needed - How to bind Sub Report to Main Report's Data.
Regards,
Stef
Telerik by Progress
There is multiple way to achiev ' fake header ' in a SubReport.
The easier way for me is :
Use Label as Header/Footer
Use Table to display the element
Use your Datasource only on the table not on the Detail Section
This is a 100% WYSIWYG solution.
I give you some quick mockup of what i did using this solution.
1rst picture is the a general solution.
2nd picture is a mock up of one of my report.
Regards,
Pierre.
Indeed you can use the GroupHeader/Footer or ReportHeader/Footer sections. Page Sections will be ignored, including PageSettings, when a report is added via SubReport item.
Regards,
Stef
Telerik by Progress
Thanks for response.
When using Gruop/Report Header, the header is on every new subreport, however, I need it to be on EVERY SINGLE PAGE of the whole report (as mentioned, report is consisted of string subreports, which are really long).
Can the PrintOnEveryPage Propeties on GroupHeader do the trick ?
regards,
Pierre.
Thank you very much :)
I am almost there, but now, on the first page of the subreport, the header prints twice, I dont understand why. Other pages of the subreport look fine now.
I just can't reproduce the behave on my side, on a clean report.
Now you have 2 solution:
1/. Submit a ticket with your code and pray the old god.
2/. Publish runnable standalone sample here.
In your quest you must have alter a properties a little one and you have forget about it .
And this is the source of your issue.
Create a new sub report a clean one.
Try to reproduce the issue.
If you can reproduce it publish it here.