duplicate rows in PDF export
1 August, 2012
Hi,
When exporting a report in PDF format, we are seeing a duplicate of the last row on a page as the first row on the next page. (see image, and attached report). We do not see the duplication in XLS or DOC formats.
I have tried the single and multiple page settings. Both had duplicates with the PDF export.
YF instance info also attached.
Please investigate the issue.
Regards,
Chris West
When exporting a report in PDF format, we are seeing a duplicate of the last row on a page as the first row on the next page. (see image, and attached report). We do not see the duplication in XLS or DOC formats.
I have tried the single and multiple page settings. Both had duplicates with the PDF export.

YF instance info also attached.
Please investigate the issue.
Regards,
Chris West
Hi Chris,
I have tested this with a few reports on the same 6.0 build and using report sections and different section options, though unable to reproduce.
Is it only the 2nd page that shows the duplicate?
Does this occur in ALL reports that span over 2 pages? (is this related to report sections)
Also does this occurr in landscape.
If the ahove doesn't help identify the issue, do you have any custom format settings, other than column headings and alternate row color?
Thanks,
David
I have tested this with a few reports on the same 6.0 build and using report sections and different section options, though unable to reproduce.
Is it only the 2nd page that shows the duplicate?
Does this occur in ALL reports that span over 2 pages? (is this related to report sections)
Also does this occurr in landscape.
If the ahove doesn't help identify the issue, do you have any custom format settings, other than column headings and alternate row color?
Thanks,
David
Q: Is it only the 2nd page that shows the duplicate?
No, the duplicates show at other page breaks as well.
Q: Does this occur in ALL reports that span over 2 pages? (is this related to report sections)
No, not all reports have the issue.
The duplication does seem to occur within a section when it breaks within the same data type.
In this case "Product". (see attached reports)
Q: Also does this occur in landscape? Yes
I exported the same report in landscape and it showed duplicates.
I increased the font size from 11 to 12 (font is Arial) and exported the report in landscape. No duplicates.
I exported the 'font size 12' report in portrait and there were duplicates.
Q: If the above doesn't help identify the issue, do you have any custom format settings, other than column headings and alternate row color?
There is no other custom formatting applied besides column headings and alternate row color.
No, the duplicates show at other page breaks as well.
Q: Does this occur in ALL reports that span over 2 pages? (is this related to report sections)
No, not all reports have the issue.
The duplication does seem to occur within a section when it breaks within the same data type.
In this case "Product". (see attached reports)
Q: Also does this occur in landscape? Yes
I exported the same report in landscape and it showed duplicates.
I increased the font size from 11 to 12 (font is Arial) and exported the report in landscape. No duplicates.
I exported the 'font size 12' report in portrait and there were duplicates.
Q: If the above doesn't help identify the issue, do you have any custom format settings, other than column headings and alternate row color?
There is no other custom formatting applied besides column headings and alternate row color.
I did a bit more investigation. I created a new report using the same view and fields. I did not add a section.
When I left the "records per page" under Table Size at the default (100) and exported the report, it was okay.
When I removed the restriction, the duplication occurred.
(see attached reports)
Chris
When I left the "records per page" under Table Size at the default (100) and exported the report, it was okay.
When I removed the restriction, the duplication occurred.
(see attached reports)
Chris
Hi Chris,
Thanks for the additional information.
I have managed to reproduce your issue and have raised it as a defect (TASK ID = 117296).
It looks like when cells are a bit wider than normal (due to font size or line wrapping) it can duplicate the last record on a page, as it doesn't fit it %100, so it throws it on the next page.
At this point in time the only work around is to add a page limit so that the page break appears just before the last record in a table.
Generally fixes are only implemented in the latest release (being 6.1 currently), though we can add to older releases if deemed necessary.
Is this something you will need in 6.0?
Apologies for the inconvenience.
Regards,
David
Thanks for the additional information.
I have managed to reproduce your issue and have raised it as a defect (TASK ID = 117296).
It looks like when cells are a bit wider than normal (due to font size or line wrapping) it can duplicate the last record on a page, as it doesn't fit it %100, so it throws it on the next page.
At this point in time the only work around is to add a page limit so that the page break appears just before the last record in a table.
Generally fixes are only implemented in the latest release (being 6.1 currently), though we can add to older releases if deemed necessary.
Is this something you will need in 6.0?
Apologies for the inconvenience.
Regards,
David
Thanks David. Yes, please apply the fix (when available) to v6.0. It will be a bit before we move to 6.1.
Best Regards,
Chris
Best Regards,
Chris
Hi Chris,
It doesn't look as though this will get fixed as soon as we were hoping.
Our developers have just found out that this is a bug in the library that we are using for creating pdfs.
Our developers have said that we are looking at rewriting the pdf stuff.
Apologies for the delay.
Regards,
David
It doesn't look as though this will get fixed as soon as we were hoping.
Our developers have just found out that this is a bug in the library that we are using for creating pdfs.
Our developers have said that we are looking at rewriting the pdf stuff.
Apologies for the delay.
Regards,
David
We have moved to 7.1. Closing this post.