Created attachment 63491 [details] Try the reports area_repeat_... - with one and two areas When you will write a bill with adressfield at the first page and headers for the columns at the first page and all other pages you will put the adress into one grouping area and the headers for the columns in another grouping area. The grouping area for the columns should be repeated. This works only with a pagebreak before and after the grouping area of the columns. The fist page shows only the adressfield.
I can confirm this bug. If the detal section of a group section, with this option set to true, needs less than one page, each group value is separated wit a pagebreak
Created attachment 64995 [details] Description: pagebreak is set while "Force New Page" is "None" I have added a description where you could find the pagebreak and the repeating of a group in the properties in report-builder. Also a picture, which shows, how the printout of this properties looks like - with pagebreaks before every group-header.
Can someone find out with what Version that problem started? Is this function correctly and completely described in Help or is additional fixing required there?
Version: How could I choose a version, when this has been a bug in LO 3.3 and also in 3.5? The problem is, that nobody recognized it before. In the description of LO-help is nothing to read about repeated areas.
(In reply to comment #4) > Version: How could I choose a version, We explained it few days ago on <discuss@de.libreoffice.org>: <http://wiki.documentfoundation.org/BugReport_Details#Version>
Have changed the version to the earliest LO-version. It already exists in LO 3.3.4 ...
Just testing all bugs from Report-Builder. This bug first appears in the oldest available version of LO, 3.3.0 beta1. So I set the first available bugzilla-version, 3.3.0 release.
Adding self to CC if not already on
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.0.4 or later) https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT: - Update the version field - Reply via email (please reply directly on the bug tracker) - Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
Bug still exists with LO 5.1.0.2, OpenSUSE 42.1 Leap, 64bit rpm Linux.
Bug appears in the first available LO-version (LO 3.3.0.4, OpenSUSE 42.1 64bit rpm Linux). So I set this bug as "Inherited From OOo".
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to "inherited from OOo"; 4b. If the bug was not present in 3.3 - add "regression" to keyword Feel free to come ask questions or to say hello in our QA chat: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Bug still exists with LO 5.3.1.1, OpenSUSE 42.1 Leap, 64bit rpm Linux.
I confirm the bug. Still exists in LO 5.4.4.1 on Ubuntu 16.04 64bit and Windows 7 64bit. Any chance to get that fixed?
** Please read this message in its entirety before responding ** To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year. There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present. If you have time, please do the following: Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the information from Help - About LibreOffice. If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice. Please DO NOT Update the version field Reply via email (please reply directly on the bug tracker) Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not appropriate in this case) If you want to do more to help you can test to see if your issue is a REGRESSION. To do so: 1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/ 2. Test your bug 3. Leave a comment with your results. 4a. If the bug was present with 3.3 - set version to 'inherited from OOo'; 4b. If the bug was not present in 3.3 - add 'regression' to keyword Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 6.1.0.3, OpenSUSE 15, 64bit rpm Linux.
Suspecting the setPageBreakDefinition in startGroupinstance and endGroup in reportbuilder/java/org/libreoffice/report/pentaho/output/text/TextRawReportTarget.java, somehow i can't figure out how to debug this though :D kdevelop just skips my breakpoints and uncommenting those lines, setting them to false or null gets rid of the area altogether, will give it another shot later
it seems like the reportbuilder goes to the page too early, while the second groupheader is added to the next best header (the one on the next page), the first groupheader is added to the page body, now i just need to figure out where those flags are set :)
Note: The bug only appears if I set repeat section. Seems the report builder want to solve the repeat by setting the content in next page header. So it has to create a new template for the page. If I execute a report and want to edit it I could see for the group header and the detail-content new templates for the page. The footer for the group is set to a new page with the same style as the first page. This design could only be solved by setting the group header as a header of the table, which saves the content of "Detail". This header should be repeated.
(In reply to Robert Großkopf from comment #19) > This design could only be solved by setting the group header as a header of > the table, which saves the content of "Detail". This header should be > repeated. Better: Put the group header in a frame. You could position the content at every place you want and let the "Detail" section untouched. When setting the group header as part of the page header you couldn't change anything by choosing page break for the header "before", "after", "before and after" or "none". No difference in the behaviour of a created report. Every time a page break before an a page break after the section "Detail" will be executed. All this couldn't be solved with changing the code only at one position.
I have searched through the java-files from the ReportBuilder to understand it a little bit more and have found this in /pentahoo/output/text/TextRawReportTarget.java: -------------- if (role == OfficeDocumentReportTarget.ROLE_GROUP_HEADER || role == OfficeDocumentReportTarget.ROLE_GROUP_FOOTER) { // if we have a repeating header, then skip the first one .. // if this is a repeating footer, skip the last one. This means, // we have to buffer all group footers and wait for the next section.. startBuffering(getContentStylesCollection(), true); } ----------------- (line 1069 ff) Seems to be wrong for me: The repeating header shouldn't be skipped. Seems it is planned to put a pagebreak before beginning to write down the header. You couldn't set this to "No". Then this: ---------------- protected void startGroupInstance(final AttributeMap attrs) { if (getGroupContext().isGroupWithRepeatingSection()) { setPagebreakDefinition(new PageBreakDefinition(isResetPageNumber())); } } ------------- Seems the page break is automatically set if there is a Group with repeating header - no way out. Could it be this feature (repeating a group header without a pagebreak before and without a pagebreak before the footer) has never been implemented and only been planned in the GUI, not in the code? Wouldn't be the first feature, which has never been realized in code, but has a button in the GUI for ... nothing.
Dear Gerrit Großkopf, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assigned it back to yourself if you're still working on this.
gerrit pushed bugfix to gerrit ( https://gerrit.libreoffice.org/c/core/+/107780/1 ) hopefully this is fine that the Bugfix is avaliable to Apache Openoffice as well, making it dual-licensed with Apache License and Mozilla Public License. Greetings, Gerrit
Dear Gerrit Großkopf, This bug has been in ASSIGNED status for more than 3 months without any activity. Resetting it to NEW. Please assign it back to yourself if you're still working on this.
Please assign this bug as NEW Version: 7.4.2.3 / LibreOffice Community Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR Calc: threaded
(In reply to TISSENDIER Pierre from comment #25) > Please assign this bug as NEW > > Version: 7.4.2.3 / LibreOffice Community > Build ID: 382eef1f22670f7f4118c8c2dd222ec7ad009daf > CPU threads: 4; OS: Linux 5.15; UI render: default; VCL: gtk3 > Locale: fr-FR (fr_FR.UTF-8); UI: fr-FR > Calc: threaded This bug is st to NEW since many years. Please don't switch the version. It has to be the first version the bug appears. So if you switch to LO 7.4.2.3 other people say: Oh, it is working in LO 7.4.1.2 - so let us see what has to be changed. This never worked, so it has been set to "Inherited From OOo"