PrintAtBottom = False not working in Group Footer Section

[Nuno]

Hello,

I have a problem with the group footer section. My objective is to stick it to the last printed row of a table in the detail section.

I have it configured to PrintAtBottom = false

On the page i have only 2 groups and in the detail i have a table. 

When the table row is too height and it doen't fit in that page, the group footer section is printed always on bottom of the page, and i do not want that, i want it to be printed right below the last row of that table in that page.

I already play it around with the keeptogether and it didn't work.

Can somebody help me?
Thanks,
Nuno

[Silviya]

Hi Nuno,

I tested to reproduce this behavior, but with no luck. The PrintAtBottom property is working as expected on my side, i.e. when false, the section is printed right after the preceeding section. When true, the section is printed at the bottom of the page that contains the section. All subsequent sections will be moved on the next page. If there is no preceeding section on the page, the section will print on the top of the page.

Please open new support ticket and send us the report definition to check it settings and give you more precise solution.

Regards,
Silviya
Progress Telerik

[Nuno]

Hi,

Thanks for response.

This only happens when the last row of the table to be printed in the page does not fit in it ... did it was your case? Did you saw the NOK.png file that i sent?

Thanks,

Nuno

[Silviya]

Hi Nuno,

As you have opened a support ticket on the same topic and we were be able to debug the report definition, let me share the result of our research here as well:
"What happens is that the last row of the table inside the detail section cannot fit the remaining space and goes on the second page. This makes the table in question to grow beyond the first page."

"This behavior of the table is by design (we haven't thought of a possibility to collapse that unused table space when the table gets split). 
So, basically, this is not a bug, but how it works at the moment. We still consider that there is a place for improvement based on this scenario.
 
A possible workaround is to move the datasource to the Report itself and feed the table with binding like: 
=ReportItem.DataObject"

Regards,
Silviya
Progress Telerik