Posted 24 February 2026, 11:20 am EST
I am building an AP check printing report using a Page Report in ActiveReports. My JSON data source returns a flat array where each row represents one invoice line, with check-level fields (payee, address, amount, MICR line, signature) repeated on every row. Multiple invoice rows share the same check number.
My goal is a standard check layout:
- Check header area: payee name, address, check date, check number
- Middle section: a table with repeating invoice lines (description, invoice number, amount)
- Check bottom: total amount, written dollar amount, MICR line, and a base64 signature image
I have the table working with a group on checkNumber and NewPage = Next to paginate per check. The invoice lines display correctly.
The problem is that fields placed outside the table (the check header and footer areas) do not change from check to check — they stay stuck on the first check’s data.
I looked at the sample invoice report that ships with ActiveReports and it appears to have fields outside the table that do change per invoice. I’m trying to understand the correct pattern to replicate this.
My questions:
- What is the correct way to have free-floating fields outside a table update per group/per check in a Page Report?
- Is a List control the right approach as the outer container, with both the free fields and the table inside it?
- Or should all per-check fields actually live inside the table as Group Header/Footer rows?
Any guidance or a pointer to the relevant sample would be greatly appreciated.
Thank you
