yet another repeating headers issue in ssrs

db042190 1,516 Reputation points
2021-11-04T12:36:13.383+00:00

hi we run 2014 enterprise. usually when i look at the properties of static row groups and change the attributes as are shown here, https://social.technet.microsoft.com/wiki/contents/articles/19398.ssrs-how-to-repeat-headers-on-each-page.aspx (and a thousand other articles), headers repeat on pg 2 to N but not this time. very frustrating. as i recall nobody really understands this nuance in ssrs sufficiently to guide people. I'm trying below to share what i have going on here without sharing proprietary info. i've also tried setting the tablix's properties (repeat headers) and that didnt work either. and i did try to set the keep with group and repeat on new page static attributes on the 2nd and 3rd row group static objects but got errors. similarly i tried the same on the 1st column group static item and got errors. and i did try keep together with the other 2 attributes on the static row item and that didnt work either. The details group has no expressions etc in its group properties. also i did try throwing in fixed data true on one experiment but it didnt help.

146562-image1.png

146507-image2.png

SQL Server Reporting Services
SQL Server Reporting Services
A SQL Server technology that supports the creation, management, and delivery of both traditional, paper-oriented reports and interactive, web-based reports.
2,793 questions
0 comments No comments
{count} votes

Accepted answer
  1. db042190 1,516 Reputation points
    2021-11-04T16:29:56.417+00:00

    i spoke with one of my peers and she explained that back in the year 2012 some sort of upgrade was done here that left an unusual static row profile/hierarchy behind on an unknown set of reports. They didn't entertain the idea back then of going into/modifying the xml, so instead, on the reports they did try to fix, they rebuilt the tablix's from scratch to correct the problem. The report I referenced here wasn't one they addressed, it might not have even been known to be a problem.

    During my conversation with my peer, she asked if static rows could be deleted. A light eventually went off in my head and i stared at the xml until it was pretty obvious what constitutes a static row in ssrs xml. I carefully changed the xml in a test copy of the report from the before "tablix row hierarchy" you see below to the after and was lucky enough to get this fixed. One of the authors out there does warn about the complications that can arise when there are multiple or nested hierarchies.

    146567-beforehierarchyxml.png

    146623-afterhierarchyxml.png

    0 comments No comments

3 additional answers

Sort by: Most helpful
  1. db042190 1,516 Reputation points
    2021-11-04T12:59:52.22+00:00

    here is the error i get when i try to set the 2nd static row 's attributes the same way. supposedly static items at the same hierarchy level should be set the same way but apparently not here.

    146563-errorigetwhensettingstaticattributeson2ndstaticite.png

    0 comments No comments

  2. Isabellaz-1451 3,611 Reputation points
    2021-11-05T02:16:34.503+00:00

    Hi @db042190

    Why in your row groups have 2 'Static' above the '=(Details)' ?Cause I see from your design report,there is only one row above the detail row
    146679-screenshot.png

    146694-my-test.png

    Best Regards,
    Isabella


    If the answer is helpful, please click "Accept Answer" and upvote it.

    Note: Please follow the steps in our documentation to enable e-mail notifications if you want to receive the related email notification for this thread.

    0 comments No comments

  3. db042190 1,516 Reputation points
    2021-11-05T10:28:28.113+00:00

    hi isabella. my peer believes that an upgrade we did back in 2012 left some reports in this weird state. i don't have any more details than that and have to assume it would be difficult for someone to do this manually and on purpose. I have another post somewhere that shows proof of a corrupted rdl file right around or having something to do with a string value. the report still ran but if i'm remembering correctly whatever ssrs did restricted me in my ability to accomplish a change i wanted to do. if i can find that post i'll show it here. it might be on a different forum.