Forum Discussion
Paginated Report headers not repeating
Hi Everyone.
I have a paginated report that is a Tablix (one column report). It has 4 Row groups within it. My header is set on the COUNTY group (2nd one in hierarchy). I have been unablee to get this header to Repeat when the report for that groups spills to another page.
What I have done
1. On Static row in COUNTY Group: Set KeepwithGroup = After; RepeatonNewPage = True
2. Set KeepTogether = False on textbox properties
For testing, I set another child group header to repeat as well but it is inconsistent across the report. Sometime it repeats, sometimes it doesnt.
Any help will be appreciated.
Hi sufregs ,
Thank you for your patience, and apologies for the delay. Also, thank you for sharing the RDL and data.
I tested a similar configuration with the same settings (RepeatOnNewPage = True and KeepWithGroup = After on the header static members, along with page breaks between COUNTY instances), and in my test the header rows repeated correctly when the same group continued onto the next page.
This suggests the behavior depends on how pagination occurs relative to the tablix hierarchy. In your report, since the data expands within nested groups (LA_PROP_CLASS and TAX_DIST_DESC_GRP), the pagination may be occurring at a different level than the COUNTY-level tablix member associated with the header, which can affect the repeat behavior.
To improve consistency, you may consider aligning the header rows with the tablix member that spans across pages, or simplifying the grouping structure.
Alternatively, if the headers are static, placing them in the report header section can ensure they appear on every page.
For Reference:
Grouping pane in a paginated report (Report Builder)Attaching rdl file for reference.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi sufregs ,
Thank you for the update.
I understand the behavior you’re seeing. When the header is tied to the COUNTY group, it may not always repeat consistently, and when tied to the child group (LA_PROP), it repeats within the same page.
This appears to be related to how RepeatOnNewPage works with nested groups, where the repeat behavior depends on the group the header is associated with and how pagination occurs.
If restructuring the grouping is not feasible, one possible approach is to keep the header at the COUNTY level and adjust the layout to reduce the impact of nested groups on pagination. Otherwise, this may be considered a limitation of the current tablix rendering behavior.
Please let me know once you are able to test the sample RDL.
19 Replies
Hi sufregs ,
I think the issue here might be the difference betwen "group header" and "table/tablix header".
If found some instructions online for you that should help you out:Even if you set
RepeatOnNewPage=True, it only works if you set it on the static tablix member that corresponds to the header row (not the group itself, not the textbox).Steps
- Click the tablix.
- In the Grouping pane (Row Groups / Column Groups), click the dropdown ▾ on the right.
- Turn on Advanced Mode.
- In Row Groups, you will now see Static items above/between your groups.
- Click each Static item and look at:
- Which one highlights your COUNTY header row in the designer?
- That is the one you must set.
Thank you for the response. That is exactly what I did for all the static members that make up the header but it still does not repeat
Hi sufregs ,
Thank you for the update.
If the properties were already set on the correct Static member in Advanced Mode and the header still does not repeat, it may be worth checking whether any page break settings on the groups are affecting pagination. For example, if a parent or child group has a page break configured (start, end, or between instances), it can sometimes affect how headers repeat when the tablix spans multiple pages.
You may want to confirm that the header row is tied to the correct static tablix member that corresponds to the row actually spanning the page break. In some cases the header appears part of a group, but the repeat behavior depends on the underlying tablix member structure.
Could you also check whether the COUNTY group has any page break settings enabled and whether the tablix has KeepTogether = False? These settings can influence pagination behavior.
More details about how repeating headers work with tablix members and group pagination can be found here:
Similar thread: Solved: Re: Report Builder Column Headers are Not Repeatin... - Microsoft Fabric Community
Hope this helps. Please reach out for further assistance.
Thank you.
Hi.
How and why would the page break happen before the content spills to another page? Page break is set to happen at the instance of another COUNTY.
To your question, yes in some occasions the content for same County spill over to another page. That is why I want the header rows repeated. On other instances, the content is able to fit a page and this works great.
FYI; My tablix is 1 column, multiple rows
Hi sufregs ,
Thank you for the additional details.I attempted to reproduce a similar layout with the same configuration (RepeatOnNewPage = True and KeepWithGroup = After on the header Static members, and a page break between COUNTY instances). In my test report, the header rows repeated correctly when the same COUNTY instance continued onto the next page.
Since the configuration you described appears correct and the behavior could not be reproduced in my test, it may depend on the specific tablix structure in your report.
If possible, could you share a sample version of the RDL file (with any sensitive data removed)? This would help reproduce the exact layout and investigate the behavior further.
You can upload your file to a cloud storage (like OneDrive, Dropbox, Google Drive or Wetransfer for example) and paste the link to that storage location in the post.
Hope this helps. Please reach out for further assistance.
Thank you.
Hi sufregs ,
Justr wanted to check in regarding your query. If you need further assistnace could you please share a sample version of the RDL file (with any sensitive data removed)? This would help reproduce the exact layout and investigate further.Thank you.
