A check-printing report (built on a repeating-record RDF layout, where any check spanning more than one page gets voided by the standard IFS logic) needs a summary/amount-details block printed at an exact fixed position near the bottom of the page — a repeating footer element can't be used because it can't bind to the specific table values needed, and simply enlarging a table cell prints inconsistently since the number of preceding rows varies.

All FAQ questions / Reporting and analytics

Answer

Since any check that overflows onto a second page is void by design in this report's standard logic, you can safely assume the content on a genuinely final page is always complete — define a distinct 'last page' footer section and hardcode its repeating-element values to zero/blank there, rather than trying to bind it dynamically to variable table data. That distinct last-page footer gives you access to place a table/cell at an exact fixed position using global report values, sidestepping the variable-row-count problem that breaks a naive fixed-position approach on every page.

Documentation-based answer. Confirm the product and release before applying it. This answer has not been verified in an IFS environment.

← Browse Reporting and analytics questions