Print Driver output omits pages due to Overset Error
By default, DesignMerge will omit a record's pages from Print Driver output if a variable text box is overset when the record is merged into the document. The Print Driver session's Summary Report will list the records that encountered an Overset Error. For example, here is a copy of a report where record number 2 and record number 4 encountered an Overset Error:
Record 2, in job Postcard, contained 2 overset text boxes, and 0 missing variable pictures. Document was skipped.
Record 4, in job Postcard, contained 1 overset text boxes, and 0 missing variable pictures. Document was skipped.
PPML Files (Disk, Count: 1, Records: From 1 to 6)
TIP: If a Summary Report indicates any Errors were encountered, it can be helpful to save the report so you can reference the report later to see which documents were skipped by the Print Driver session (which pages were omitted from the Print Driver output). To save the report, simply click the Save Report button on the bottom of the Summary Report window.
Before committing to a Print Driver merge session, you can test your document for potential Overset Error conditions by running a Longest Line Test merge session, as described in Tutorial #2 (Postcard) in the DesignMerge Tutorial Manual, available in PDF format in the DesignMerge product folder on your system. See the I need help finding an overset text box (overset text frame) Knowledgebase Article if you are having difficulty finding any oversets.
If the Longest Line Test does not reveal any potential oversets, but the Print Driver still indicates records encountered an Overset Error, you can run a Merge Current Document Test merge session to determine why these records are encountering an Overset Error. For example, if record number 2 encountered an Overset Error, run a Merge Current Document Test on the Record Range From 2 To 2. You can then review the merged document to determine why the data for this record caused an overset.
When determining why variable text overset, please note that Hyphenation and Justification settings may cause an overset for a particular record's data but not for the Longest Lines.
Also, please note, if you are using a Cut & Stack mode for the merge session, a Stack Pad condition may cause an overset. TIP: Before committing to a Print Driver session, you can test whether a Stack Pad condition will cause an overset by simply editing the Text Links in the document to display the text "Stack Pad" or you can run a Merge Current Document Test merge session to produce the last page of Cut & Stack output. To do this, open the DesignMerge (merge) window. Select Stack Range for the Sequence Mode, and enter the appropriate record number for the Record Range. To determine which record number will produce the last page, divide the total number of records by the number of ups (the highest sequence number) in the document. If the total number of records is not evenly divisible, add 1 to the result. The resulting number is the record number for the last page. For example, if you are merging 8 records into a 2-up document, on the DesignMerge (merge) window, select Stack Range for the Sequence Mode and for the Record Range, enter From: 4 To: 4. If you are merging 9 records into a 2-up document, enter From: 5 To: 5.
There are several different methods that may be used to avoid an overset, as described in Tutorial #2 (Postcard) in the DesignMerge Tutorial Manual:
If your document's design allows, you can modify the formatting of the text or the size of the text frame to accommodate the Variable Text from all records and, if applicable, to accommodate a Stack Pad condition.
You can use CopyFit with DesignMerge to fit oversetting Variable Text on-the-fly while merging, as described in Tutorial #2 (Postcard) in the DesignMerge Tutorial Manual.
If the only Links that will cause an overset are Stack Pad Links, then you can change your default DesignMerge Preference to process/print pages that encounter an Overset Error. To do this, open the DesignMerge Preferences window by selecting Preferences from the DesignMerge menu. On the Preferences window, click the Errors button. This opens the Errors window. On the Errors window, open the Overset boxes popup menu and select Process Anyway. Then, click the OK button to close each window. NOTE: Once you have finished producing the output for the current job, you may prefer to change your Overset boxes preference back to the default setting Skip Job. For more information about DesignMerge Preferences, see Tutorial #5 (Tips & Tricks) in the DesignMerge Tutorial Manual.