SSRS (Reporting Service) report layout with mulltiple breaks and expression in show/hide property. - by KM IT

Status : 


Sign in
to vote
ID 785850 Comments
Status Active Workarounds
Type Bug Repros 0
Opened 4/29/2013 5:33:48 PM
Access Restriction Public


Hello SSRS team (2008 R2 or 2012 version),

This is a bug/feedback about limitation of SSRS report layout design with multiple breaks. Below are the details:

I.e. on report, I have requirement to break report design layout in multiple area such as Report Header, Body and Report footer. Of course header and footer are available on SSRS. However further in requirement, I have to split report body in various sections such as body header, body part 2, body part 3, body part 4, body footer, etc... And each of this body part should have property like fixes position when report is render and in my case each body section has a sub-report. Now limitation with SSRS is that during the report execution, it display sub-report1, sub-report2 and so on from top-to-bottom (with current design) but I would like to have last sub-report as part of body footer [show at bottom of the body always] which cannot be done. To display data with fixed position on footer I have to do ReportItems!MyField.Value concept to show on footer. Jasper report supports all these complexity to design complex report

I hope MS SSRS team include feature (with advance property) to split report body in multiple section. 

Also one more feedback on new improvement on Show/Hide property in visibility section I.e. if I have textbox1 has show/hide based on textbox2 then on tablix, I can't write expression like =Iif(TextBox1.Visibility="Hide",...,...). So apparently in show/hide property, SSRS expression is not allowed to write.

Hope to see these features in new service-pack!
Sign in to post a comment.
Posted by Microsoft on 6/2/2014 at 3:13 PM
Thank you for submitting this feedback. After carefully evaluating all of the bugs in our pipeline, we are closing bugs that we will not fix in the current or future versions of SQL Server. The reasons for closing these bugs are following:
1.     The fix is risky to implement in the current version of the product (service packs)
2.     Scenarios reported in the bug are not common enough
3.     A viable workaround is available
Thanks again for reporting the product issue and continued support in improving our product.
Matt Jones
SSRS Tiger Dev Team
Posted by Microsoft on 5/14/2014 at 10:33 AM

Thank you for submitting this feedback. We are investigating the issue and will update you when we have more information.

Matt Jones
SSRS Tiger Dev Team