Last Updated: 04 May 2016 13:44 by Steve
Created on: 21 May 2014 15:02
Type: Feature Request
Nested tables should not be kept together
Keeping nested tables on the same page causes huge empty spaces on multiple pages. This is definitely not a proper way for implementing such things. This feature request is caused by this forum response:

Please do not reply with 'grouping', crosstab or other proposals because data grouping has other limitations. Also please note that nested table is pretty common simple scenario for situation when data already is grouped which is almos always the case of ObjectDataSource scenarios.

Impact: Currently these half-empty pages cause report to look low-quality which is not acceptable for our clients. 
Posted on: 23 Sep 2015 14:33
It's been pretty clear over the years that report quality is a low\no priority
Posted on: 23 Sep 2015 14:18
Similar topic, the same thing happens in a simple table. I have a report with comments as a table item and the comments field grows too large to stay on one page.  This then renders on the next, causing the exact issue described here: White space between report objects causing the rendering in PDF to look low-quality.  It seems the "KeepTogether" = False property is not being respected within a table cell?
Attached Files: