I suggest improvements to Combination Print:
- Functions or variables to determine the (global) page number of the first page of the current project and the current (relative) project page number. Use cases: Often you want to design the first page of a project differently from the following pages. When dealing with pre-printed forms all pages are structured differently.
- base the project setting “minimum page count” on the project it is set for instead of on the whole combination print job. Use case: An official preprinted form needs to have x pages independendly from it’s position in
AutoProjectFile. - Allow to skip a project in the
NextCombinationPrintStepevent. Use case: When retrieving data on demand or in the background while the first projects are printing you might have an empty result set and don’t want to print an empty page. - Allow to switch between
AsVariablesandAsFieldswithout resetting the combination prints page numbers. Use cases:AsVariablescomes in handy when dealing with single record data, text based layouts, forms and whenever you need to freely position data bound objects on a page. Currently you can’t useAsVariablesin combination print without loosing contiguous page numbering and report-spanning TOC/IDX. - Fire
NextCombinationPrintStepalso for TOC/IDX projects