Acidus Posted July 10, 2013 Share Posted July 10, 2013 I'll explain the problem using attached image.I have 2 detail bands. First band is max size and at the bottom there are 4 elements, two of those are blank and are removed (because of "Remove line when blank" property), so there is free space for 2 elments from second detail band. When report is compiled, elements "detail 1.3" and "detail 1.4" are removed and elements "detail 2.1" and "detail 2.2" apear in their place on first page (element "detail 2.3" remains on page 2). So it works OK! BUT - when I set element "detail 2.2" as blank, compiler removes it only in second band. When elements are shifted to first page, compiler suddenly thinks that previously removed element "detail 2.2" is still visible and draws a blank line. Element "detail 2.3" of course stays on page 2 insted of moving to page 1.How can I force it to move "detail 2.3" element to page 1 when element "detail 2.2" is removed (blank) or is it a bug? Link to comment Share on other sites More sharing options...
lucianc Posted July 10, 2013 Share Posted July 10, 2013 Could you post a JRXML (with some static data) that illustrates this? That would be easier to follow.. Link to comment Share on other sites More sharing options...
Acidus Posted July 10, 2013 Author Share Posted July 10, 2013 Sure! I added jrxml file to my first post. Problem can be seeen by changing element "detail 2.2" print expression. If it is printed then it will appear in page 1. If it is NOT printed then it will still appear in page 1, but as a blank line. It should have been removed by "Remove line when blank" property. Actually if I am doing it right then it might be a JasperReport problem not iReport. Link to comment Share on other sites More sharing options...
lucianc Posted July 11, 2013 Share Posted July 11, 2013 It does look like a bug, please log it in the trackers. Not sure for now if there is a workaround for it.. Link to comment Share on other sites More sharing options...
Acidus Posted July 11, 2013 Author Share Posted July 11, 2013 I logged it in the JR library tracker. Please inform if you come up with some kind of workaround. Thank you! Link to comment Share on other sites More sharing options...
teodord Posted October 28, 2019 Share Posted October 28, 2019 Hi,I have closed the tracker at:https://community.jaspersoft.com/jasperreports-library/issues/3056-0by providing some workarounds, as this works as designed.Thank you,Teodor Link to comment Share on other sites More sharing options...
Recommended Posts
Create an account or sign in to comment
You need to be a member in order to leave a comment
Create an account
Sign up for a new account in our community. It's easy!
Register a new accountSign in
Already have an account? Sign in here.
Sign In Now