Can anyone explain the paging that is happening in this report?
Ive set KeepTogether = false everywhere I can think of. Also Group Keep Together is false.
But it is still throwing pages as if KeepTogether was true in some places.
7 Answers, 1 is accepted
The files you attached are not accessible.
Check if Detail section's KeepTogether property is set to False. The same applies for Detail sections of subreports if you have any. The Problem: Telerik Reporting renders blank pages KB article provides further details how to troubleshoot the issue.
If the issue persists, please attach a problematic report in a support ticket so we can check the settings.
Regards,
Katia
Telerik
Hi Katia
Thanks for your response!
I tried to submit a ticket but I need to be associated with a license so I need to find out how the licensing works in this situation. Our client is using Cebos and I believe their licensing of Progress products all happens through QAD. Could take time to track down the relevant license info ... unless you can give me some clues to finding licensing info through the product itself.
I included attachments with the post which were the trdx file and sample output in pdf format. Just download them and remove the .jpg extension to see the files.
Hi Katia
The Detail Section keepTogether is already set to False
The consistent behaviour is:
If the embedded table is less than a whole page in itself then the keepTogether works and it will span a page.
But if the embedded table itself exceeds 1 page then it switches to keepTogether behaviour.
Hi Katia
Did you manage to download those files?
Yes, I examined the files you attached and noticed that you are using nested tables which were causing the empty spaces.
As of R2 2016, breaking of nested tables is possible - check release history(Improved Table/Crosstab item pagination). To force nested table to break set KeepTogether=False for parent table's row that contains nested table.
Attached you can find an example demonstrating this improved paging mechanism (can be opened with the latest version of Standalone Designer).
Regards,
Katia
Telerik
We have updated to R2 2016 and we are still experiencing this issue.
Can you assist me in logging a Support ticket to resolve? This has become high priority.
Thank you!
Please check my reply the support ticket you opened on the same question.
In general, to force nested table to break you need to set KeepTogether=False for parent table's row that contains nested table.
Regards,
Katia
Telerik by Progress