I have this report. I'm using a large table over the whole page with a header. Inside the details of the table I've got a table group. Group 1 is always the same size and group 2 has a variable size based on how many rows it contains, so group 3 will flex up or down depending on results. This report looks great and is exactly what we need, as long as it stays on the same page, and there is usually plenty of room on the page.
However, if there are a large number of chemicals (group 2 rows) or materials (group 3 rows), there exists the possibility for group 3 to get pushed off the bottom of the page. But the problem is... no second page ever appears. I have tried everything I could find in the documentation and these forums and nothing will make the second page show up. In testing, I tried making the overall table larger, and it appears that Ignition is still attempting to render everything on the first page, with group 3 just showing up off of the page. But... I need to be able to print this. I need that second page.
This is on both Ignition 8.1.53 and 8.3.3, by the way.
Excuse the simplicity of the question, but are you testing by looking at the 'Preview' tab in the report configuration tool in the Designer or have you actually exported a full report that should have multiple pages and observed it to be missing information? The preview tab often cuts off results with seemingly arbitrary limits (I would suppose it depends on datasource/information density in some way). I had the same thing happen last time I worked with reports -- preview was always truncated, but complete multi-page reports were as expected in the exported file.
Both. I've run it locally in Preview on a test system with trial licensing. I've also exported it to a full licensed system and run the report within a page in Ignition. Same issue persists in both settings.
So... the overflow behavior is not on the table group, table, or even details, where that feature would make sense. It's on the text fields?
Hm. I may need to play with this more. That doesn't fix it, but it does change the behavior. It renders identically if group 3 is partly cut off the page, but now, if group 3 is completely pushed off the page, it instead only renders what would have been page 2, completely cutting out page 1. This isn't good, but it is different, so maybe we're on the right track.
So Ignition reporting just doesn't support doing this?
I'm looking into whether I would be allowed to move the QC table into the header. That would let me expand the materials table enough so that no descriptions would ever take a second row of room, and then I don't know if we'll ever have so many chemicals and materials in a single charge that it would extend to a second page. That won't solve this issue, but it might become pointless for me to solve.
The header is now a table by itself, and then the main page is a table group. Within the table group, sections 1 and 3 are just a single table, so those groups are assigned named queries for their keys. Group section 2 is a table of two tables, so the group is instead assigned to a blank parameter with a value of "". This forces the group to only pull a single row. Then the underlying tables won't be repeated for every row of a query. Those underlying tables then have named queries as their data keys.
And as for pagination? Page 2 looks like this:
