I have a report with 2 subreports. When the 1st subreport is pretty long (but still leaving a good few cm on the page) and the 2nd empty, I often get an extra page printed with only page header and footer.
The subreports and sections are set to be suppressed when blank and it seems to work: I tested this by setting different colours to them and they don't appear. The strange thing is that when I set the section with 2nd subreport to be suppressed for good, the blank page is not printed.
I already switched the New Page After for all the sections, added Not OnLastRecord formula to it and suppressed or deleted all the empty sections in the subreports and around them and still no luck.
I would appreciate any suggestions.
Here are a couple things you could check that aren't addressed in your question:
right click on your subreport and select "Format Subreport"
on the common tab, uncheck the box that says "Keep Object Together"
on the Subreport tab, in case you are suppressing it another way, check the
box that says "Suppress Blank Subreport".
I hope this helps.
Related
I've had some testers reporting an intermittent issue on a search page that contains a list.
They say when they have been on the page and navigate to a sub page then return that the list is sometimes scrolled all the way to the bottom of the screen.
I've disabled tensile drag on the list, but I wanted to know if there was any other work-around for this issue?
This has nothing to do with tensile drag. When you navigate from one form to another in the old GUI builder the form is re-created from scratch and re-positioned based on the data.
We try to select the previously selected item but if something in the list changed this might trigger issues.
You can override restoreComponentState in the state machine with a blank implementation to see that this is the cause of this behavior. Assuming that it is you can create a special case for the list instance.
I've got a number of buttons in a view and have assigned a tag number to each for identification in code. I just went back to check one of them, and can't find the field in the Attributes Inspector where I originally assigned the tags. I've tried all my buttons and restarted Xcode, and the result is the same--no tag field.
Here's what my attribute inspector looks like with a (tagged) button selected in the storyboard:
I came upon a recent comment by someone who also couldn't locate the tag field. He also is using Xcode 5.0.2.
Anybody else run into this?
Thanks!
The sections in the attributes inspector can be shown or hidden by clicking on the lines where the words "View", "Control", etc appear. When you rollover the line with these section titles, you'll see the words "show" or "hide" appear on the right edge of the line. Clicking anywhere on the line toggles between the two states.
Where it says view: Move your mouse over to the far right and something should appear that says "Show". Click on it and you'll see the tag identifiers, etc.
We are developing a BI Publisher invoice print report using RTF layout. This report prints the customer details at the top of the page, followed by the invoice lines' details, and a summary table (of amounts and taxes) at the bottom of the page. Brought-forward are carry-forward totals are displayed at the top and bottom of each page (in case of multi-page reports).It is important to maintain the consistency of the print format (so that the customer address is always at the top left corner of the page, summary table is always printed at the bottom etc). To print the summary at the bottom of the page for each invoice, we have used the tag with section break, as recommended in the user guide. This works fine in situations when the invoice has multiple lines spilling over to the second page.
However, we are facing an issue in a particular scenario : Invoice has few lines that fit in the first page itself, but there is no space left to print the summary table in the same page , so the summary table alone is printed in the second page at the bottom. In this case the carry-forward total in page 1 and the brought-forward total in page 2 are not being displayed. If you have observed a similar issue anytime please suggest how to fix this.
Consider separating your sections and not using Word's header and footer.
Place this code at the start of your document
<?initial-page-number:'1'?>
<?call-template:tHEADER_VERSO?>
<?start:body?>
<?call-template:tHEADER_RECTO?>
<?call-template:tCONTACT?>
<?for-each#section:On_Payment_Terms_S3?>
<?call-template:tDETAILS?>
<?end for-each?>
<?end body?>
<?call-template:FOOTER?>
Then to define a section
<?template:tFOOTER?>
insert content here
<?end template?>
That way the document will always preserve enough space to print your carry-forward totals. I experienced the same odds results when you put your carry-forward in the Word's footer.
I have a form which has a table which may contain 0 rows or several rows.
The problem is that if there are several rows I want close the table on the first page before the content spills over to the next page. Then create another table for the rest of the rows on the next page along with a nice header and table headings. The hard part is, because characters have different widths and I can't predict what the user will type, it's hard to calculate how many characters can fit on a row and how many rows can fit on a page. Also if the user types something in some of the row data, it wraps to a 2nd row.
The printout looks bad when the row has only a few rows because there is a lot of whitespace on the bottom so I was thinking of adding in blank rows to fill it up. But again, I won't exactly know how many rows I need to fill before it spills onto the next page.
Does anyone have a solution to this?
EDIT:
Sorry about that. To be more clear on what I'm doing, I created a form view using CF and HTML which mimics visually like a paper invoice. Invoice line items can be added in dynamically via AJAX. There's a bunch of info to be filled out on top (Company name, address, etc), then in the middle there's the invoice lines in a table with column headings, then under it there's more info to fill out including signature fields. This format cannot be changed as it is a requirement.
So the form layout is:
Top section (info including customer info and a bunch of other things)
Middle section (table of invoice line items)
Bottom section (a bunch of other info including signature fields)
Visually on the page the above format is maintained and if there's a lot of invoice line items added, the page just scrolls and the bottom section is still at the end.
An unlimited number of invoice lines can be added so if you simply just print the page, the invoice lines will overflow onto the next page and the "bottom info" including signatures will be on whatever page the last page may be, which is undesired.
I need it so that whatever number of lines that can fit on the first page without having the form overflow be displayed on the first page along with the "bottom info" including signature. The extra lines are displayed on the next pages with headings "Continuation Page" along with the table column headings of the invoice lines.
My solution is to create a "print view" which creates the form with entered info and cfloops the invoice lines query but only loop just enough to fill the first page. If the addition of another row makes the form overflow then I would stop the loop, display the rest of the form with the "bottom info" and signatures so it all fits on the first page nicely, then do a page break with the header "Coninuation Page" and display the invoice line table with column headers and the rest of the invoice line items. Of course if the continuation page is going to overflow then I would need to do a page break and repeat the "Continuation Page" process. The tricky part is how to determine how many lines can actually fit on the page because the length of data in each row varies depending on user input. Maybe only one invoice line row filled with tons of data is all that can fit on the first page without having the form overflow. Maybe it's 10 invoice line rows when little data is entered.
My main purpose is to keep the entire form on the first page. If several invoice line items are added which pushes the bottom of the form onto the next page then I want to display only enough invoice line rows to keep the form on the first page and have a Continuation Page for the rest of the invoice lines that didn't fit on subsequent pages.
Note: The print is done via a print link on the form page which pops up the print view page (without site heading, etc.) in another window. From there they can either print from the browser or click on a print link that does a javascript print. the same "print view" I created to print the invoice nicely is also used for a PDF view created using CFDocument. The number of characters per line is not the same in the generated PDF as the HTML print view so it's even harder to determine how many rows can fit.
If I understand your question correctly, then a PDF generated with CFDocument would seem to be the optimal solution. Using the cfdocumentitem tag you can specify headers and footers, which insure that the content you want appears on the first page. The cfdocument.currentpagenumber variable can be used to insure that it only appears on page one, and that the header on pages 2+ display the "Continuation Page" text that you desire. There is also a way to get the PDF to auto-print using a DDX file, though that is subject to security limitations.
You mention using CFDocument to create a separate print view, but I didn't see an explanation as to why an HTML version was required as well. I apologize if I missed it.
From personal experience with a similar project last year I would tend to recommend against using CSS for this and instead just require a PDF reader. It's possible that someone with more skill than I could make it work easily, but it was nothing but a headache for us and we could never get it to work quite right.
For some reason my page footer with the date and page x/y gets only printed on the very last page. Does anyone have an idea why?
I am using JasperReports 3.1.2 and iReport 3.0.0.
EDIT: just for the record: it worked after I moved two subreports and two page breaks from the Title band to the Detail band. Don't know why I put them there, but now it works..
You can select which band to add. just use page footer instead last page footer. Last page footer is used when you want something to be printed at last, but the contain is so much that it overflows to many pages.
Most probably you are using the `Last Page Footer' band, instead of the 'Page Footer' band.