Unplanned
Last Updated: 10 Jun 2026 07:35 by ADMIN
Chris
Created on: 03 Jun 2026 21:06
Category: Reporting
Type: Bug Report
1
GroupKeepTogether should avoid a header row being orphaned from its group data

The attached sample has a simple table with two row groups, and "header" rows created via "Insert Row -> Outside Group - above".
The groups have "keep together" set.

But despite this, the header rows render at the bottom of one page, with data rows on the following page. This should never happen, I can't think of any case it would be expected (it would be like having "Chapter 2" at the bottom of a page when the text for it starts on the next page). 

I also have a sample with just 1 row group, but with 2 detail rows, and the same thing happens. It only appears to work when there's just 1 row group and 1 detail row.

Attached Files:
1 comment
ADMIN
Todor
Posted on: 10 Jun 2026 07:35

Hello Chris,

Thank you for the valuable feedback and the sample report demonstrating the issue.

Indeed, a practical or intentional use case in which a table group header appears at the bottom of a page without an associated data row is hard to find. This scenario can confuse users and disrupt the logical flow of grouped data, like your book-chapter analogy.

We will discuss further within the team how exactly to handle this, as currently the GroupKeepTogether for Tables is a boolean, whereas Report Groups GroupKeepTogether is an enum.

Regards,
Todor
Progress Telerik

Love the Telerik and Kendo UI products and believe more people should try them? Invite a fellow developer to become a Progress customer and each of you can get a $50 Amazon gift voucher.