jwindberg

Did you solve this? I'm trying to figure it out now myself. Thanks

after many years, I'm still trying to figure out how to do this. Has anyone solved this? printWhen (OnLastPage), while in the background. I still don't understand why we could not have a PAGES variable that knows how many pages in the report, or ON_LAST_PAGE or something, all these "solutions" involving stuffing things into the report parameters map are just awkward.

Did you get a reply? I'm looking at the same issue.

No. I'm frustrated with Jasper and the designers of the tools failing to recognize that such an ability could be so necessary. They were worried about how messy their code would get. I've pointed out that every credit card bill or multipage invoice is now not really possible with jasper. Didn't help.

I have a text field that is two lines tall in my detail area, and I need to not have it break at the bottom of the page, leaving one line on one page, the other on the next page. What does "Print in first whole band" do? Does it do what I want? I have the ultimate guide, and Heffelfinger's book, not that either are very good at the details of such things. Is there somethine else that will do what I want? Thanks

what section would you use for totals at the end of the detail area if not summary?

I\'m hoping a "fake summary" would flow immediately after the detail area like a normal summary, and still work with a report that is normally only one page, but I\'ll give it a try. My one report has grown into quite a collection of work arounds and hidden variables, and dummy groups. I can no longer open it with iReport. Thanks for your guidance. It would be wonderful if the title and summary sections were less special, or had options to become less special. Perhaps that is a feature that would be doable? following the rules they would be included in first/last page calculations and then various reports could use them for tricks like what I\'m doing with the dummy groups without having to resort to dummy groups.

I\'m open to suggestions. If you look at a credit card bill or a bank statement, you may very well see lines on the edge of the paper. One line on every page, save the last page, where two lines would be present. Those lines are for the machine that takes the bill and stuffs it into the evelope. My planned use of NUMBER_OF_PAGES would not have changed the number of pages, but would have allowed me to place those lines on the last page (in the back ground), which I despererately need to be able to do. LastPageFooter is failing me, as it is not always on the last page. If the data detail area causes the summary (which in my case is one line of totals) to be all alone), then the lastpagefooter is on the second to the last page. I\'m not entirely sure having the marks so low is going to work anyway, they prefer to have them near the middle of the page. How about something in the print when expression of lines, fields, and graphics so they they show only on the last page, but do not affect report length at all? That would be true for footers now anyway. If you supress a footer with page_number != 3 then you still get a big white space mind you, headers don\'t seem to work that way. They colapse.

My goal in this has been to have things appear special on the first and last page of a report. These things include the tear off section of an invoice and the last page double bar marker needed by the pitney bows machine. I don\'t care how the solution is acheived, just that a solution is found. I\'ve been suggesting a firstPageFooter, and a NUMBER_OF_OF_PAGES_IN_REPORT variable. The forum should have been a better place to discuss such designs, but I got better response here. If a firstPageFooter band, a NUMBER_OF_OF_PAGES_IN_REPORT variable, and the background actually printed on the summary, when the summary printed alone on the last page, then I woud have been done with my report in the first couple of hours. None of those three things would have been a great suprise to find in Jasper.

No, it doesn\'t make any sense. And it doesn\'t work either. It\'s from this forum page: http://www.jasperforge.org/index.php?option=com_joomlaboard&Itemid=215&func=view&catid=8&id=19023#19023 I\'ve effectively given up on the first goal of having a first page footer that is different than the rest of the footer\'s. Even though I can think of reports that need that, and need a footer with a different sized footer on the first page. This is about being able to print a graphic or a line on the last page and knowing you are on the last page, even if the last page is the summary. The graphic is the indicator to an automatic folder/envelope stuffer, and the double bar mark needs to be on the last page. I had been battling with last page footer. That restricts me to placing the graphic on the bottom edge. I really need the two marks on the right margin edge, so I had planned them on the back ground with a print when expression that was "on last page", but no such thing exists. The work arounds form the forum do the strangest things, and screw with iReports, and don\'t work with summaries, etc. I\'m back to where I started. If jasper simply supported basic functionality like firstpagefooter, lastpagefooter, firstpageheader, lastpageheader (and those really were on the first/last pages, no matter if there was a summary), and for me, most importantly, a report variable that was number of pages in report, so that I could know I was on the last page, then this report, which has been under construction for a month, and has become so complex that iReport messes it up, would have been so simple, and would have been done in a day. Yes, I can understand trying to keep your code simple, but it should not be at the expense of users who are having to fight with complex work arounds, with hidden variables, and mysterious "auto" evaluations, and unknown effects. I\'ve paid for the pdf documentation, and it\'s wrong. last pageFooter shows up on the second to the last page if the summary is on the last page. The weird trick described on the forum to get a graphic to show on the last page on the back ground fails when the last page has just the summary. I really wanted to use a line anyway, the work around only supported a graphicExpression. If a printWhen expression for a line could have been crafted that knew when we were on the last page (even if it was the summary, I\'m going to harp on the summary over and over, cuz the last page is the last page is the last page), would be such a boon. Egads, If I was using crystal, or Oracle Reports, or 4D, or nearly anything else I remember from years ago I would have been done by now. I took the challenge of trying an open source project, and wanted to help make it better by making suggestions that would make the product better for those who use it, not those who write it. I\'m sorry, this is probably not the best place or time for a rant, but I\'m tired, and I have a terrific headache, and when I discovered yesterday that the lastPageFooter was actually coming out on the second to the last page I nearly cried. WTF?

How do I get the lastPage footer to actually be on the last page even if the report has a summary section that consists of nothing but a one line of totals, but that total has the potential to fall onto its own page? It would appear that if the summary is on its own page, then the lastPageFooter is on the second to the last page, and the actual last page, gets no footer. My lastPageFooter has graphic mark used by an automatic folder that stuffs the reports into evelopes. It is very important that the mark be on the actual last page. It would seem to me that lastPageFooter is false advertising.

I suppose the code in jasper may be simpler. The code in my report template is not. And it certainly is not reliable. I\'ve been trying the weird auto based imageExpression trick from the forum to get something to appear only on the last page, and random things all over the page are vanishing. It just isn\'t working. The mere existance of: $V{PAGE_NUMBER} in my template is causing all sorts of problems with things just not displaying. This is not simple code. Not for the users of jasper, anyway.

ok, so we need to print hundreds of invoices. These invoices get feed to a pitney bows folder/evelope stuffer. You print a single line on every page, except the last one so that the folder knows which is the last page. How can I reliably print something on the last page of a jasper report? and if you say, lastPageFooter, I will tell you, "not if the summary falls onto the last page by itself". and if you suggest doing this: <variable name="CURRENT_PAGE" class="java.lang.Integer" resetType="Page" calculation="Nothing"> <variableExpression><![CDATA[$V{PAGE_NUMBER}]]></variableExpression> </variable> <background> <band height="432" isSplitAllowed="true"> <image evaluationTime="Auto" hyperlinkType="None" hyperlinkTarget="Self"> <reportElement x="564" y="400" width="30" height="15" key="image-7" /> <box topBorder="None" topBorderColor="#000000" leftBorder="None" leftBorderColor="#000000" rightBorder="None" rightBorderColor="#000000" bottomBorder="None" bottomBorderColor="#000000" /> <graphicElement stretchType="NoStretch" /> <imageExpression> $V{CURRENT_PAGE}.equals($V{PAGE_NUMBER}) ? <![CDATA["C:\dev\projects\reports\WebContent\WEB-INF\reports\finance\graphics\omr_end.jpg"]]> : <![CDATA["C:\dev\projects\reports\WebContent\WEB-INF\reports\finance\graphics\omr_start.jpg"]]> </imageExpression> </image> </band> </background> I will tell you, that, for whatever reason, nothing prints on the last page. No, really. Nothing. ok, I give up. I'm going to start coding directly in iText or something.

damn damn damn damn on a report where the last page only gets a summary, this trick fails. If I use the lastPageFooter, that fails as well. The lastPageFooter prints on the second to the last page, while the summary prints on the last page. The mark I'm trying to put on the last page is for an automatic folder. The mark MUST be on the last page, and it must be in the same postition on the page as it is everywhere else on the report.

The mere placement of <variable name="CURRENT_PAGE" class="java.lang.Integer" resetType="Page" calculation="Nothing"> <variableExpression>$V{PAGE_NUMBER}</variableExpression> </variable> in my template causes things in the header, footer, and intro to vanish. I take it out, and the report works again.

I need to have number_of_pages_in_report to know if I\'m on the last page, or if I\'m on the first page, and there will be others. The trick described in the forums caused all sorts of side effects with things in the headers vanishing, and played havoc with iReports.

Then how about NUMBER_OF_PAGES_IN_REPORT as a report variable? I tried the work around described in the forum and various objects in my header started to disappear. I fear undocumented work arounds that have unexpected side effects.

Admittedly it has been many years since I did extensive work with reporting tools, so my experience is very out of date. However, I remember tools that were fairly mature and had many ways of doing things, and were often obvious. Creating dummy bands to fake out the lack of a firstPageFooter is not obvious, nor is it easy. My argument at this point is less about my own needs and more about making jasper appear a more mature and robust tool for corporate use. Just because there is a complex and difficult, yet possible work around for a lack does not rule out the inclusion of a potentially useful feature.

The solution is not a solution. What I need for this report is a first page footer that is a full 4 inches tall, and the following footers be only a half inch tall. You can suppress things, but not actually change the height of the footer. If jasper is supposed to compete in the corporate world, and not just be an incomplete open source product, it needs to have more a more mature feature set. Not knowing that you are on the last page is a serious failing, for that matter. I\'ve been forced to start reviewing non-open source products.

I'm creating a report that is effectively an invoice. The larger detail area would be charges, and is likely to span multiple pages. The second detail area is payments, and I had planned on using a subreport, placed near the bottom of the title. The thought was that the payment area would likely expand to no more than about 10 rows, and would push the title area down as needed. Apparently, this is not the case. The title cannot grow in size. What is happening is that when the subreport gets longer, it just prints right over the top of stuff below it. Any idea how I get the effect I need? A short "payments" detail area to happen first, before the main "charges" detail area later... Thanks

If I understand all that, I think I can get my report to work that way. So far, in one report, I have had to do four complex work arounds that I can barely understand using dummy objects, and nested subreports. If a complete collection of first/last header/footer plus a NUMBER_OF_PAGES_IN_REPORT were available in the tool in the first place, my report would have been done the morning I started it, instead of weeks later. Please don't read too much into my frustration. With wonderful open source tools available for much of what I do, I don't get funding to pay for commercial tools, so I'm often times stuck using only open source, and in many cases they are better, and I do so much appreciate your help, but with a few extra features so many things could be so much easier to do with Jasper.

For that matter... What the heck does evaulationTime="Auto" mean? It's not in my book, "Jasper Reports for Java Developers". It seems to be capable of comparing now to then, but how does it know what I intend. It works, that's cool, but such black magic scares me so.

That looks close to what I need, but I failed to explain that I was trying to do this with a line. How do I specify evaluationTime="Auto" on a line? <variable name="CURRENT_PAGE" class="java.lang.Integer" resetType="Page" calculation="Nothing"> <variableExpression><![CDATA[$V{PAGE_NUMBER}]]></variableExpression> </variable> <line direction="TopDown"> <reportElement x="565" y="390" width="29" height="0" key="line-14"> <printWhenExpression> <![CDATA[new Boolean($V{CURRENT_PAGE}.equals($V{PAGE_NUMBER}))]]> </printWhenExpression> </reportElement> <graphicElement stretchType="NoStretch" pen="2Point"/> </line>

There's the trick. There does not seem to be a way to know the current page and the total page count at the same time. There is one variable, PAGE_NUMBER, which is evaluated either at "NOW" or at "REPORT", but you can't know both at the same time.

I'm having a similar problem. I'm printing a whole lot of invoices. The last page of each invoice needs two tick marks on the right edge, the other pages need one tick mark. They are used by the pitney bows folder/envelope stuffer. I had high hopes of placing two lines on the background and then marking one of them with a print when expression that meant if lastPage. However, there does not seem to be anyway to do that. I had been expecting to do new Boolean($V{PAGE_NUMBER}.equals($V{PAGE_COUNT}) But I only just found out by digging through the source code that page count is not the number of pages, but the number of records so far on the page. So, I'm stumped, and this is a complete blocking issue. I may need to go use another tool. Is there any way to display something in the middle of the page on the last page?