Created attachment 128128 [details] repeated value is not shown I the report builder if I set "print repeated value on group change" to yes it won't show up in the actual report. You can see this bug here too https://youtu.be/tuqM0_0hXdw?t=5m42s
Have had a look at the screenshot. I can't recognize what grouping you are using. So please attach an example-database and not a link to youtube or a screenshot, where nobody could know, what you expect as value for "Department".
Created attachment 128192 [details] example database @robert I've attached the database now, do you need anything else?
(In reply to Matteo Paolini from comment #2) > Created attachment 128192 [details] > example database > > @robert I've attached the database now, do you need anything else? I will now have a look on the report odb69-Employee-Info+Phone1 Could be I will give a feedback later in the evening.
Have tested with the attached database. Seems "Print repeated value on group change" has no function. Expected behavior is, when the group will be changed there must be a value and no empty field. At this moment no value appears. Also it is has no effect to set "Print repeated value on group change" to "No". Expected is here, that no value should appear when the group has been changed. But every value appears if "Print repeated values" is set to "Yes". Tested this with OpenSUSE 42.1 64bit rpm Linux, LO 5.2.2.2, LO 5.3.0.0alpha1, LO 4.4.7.2 and also LO 3.6.7.2 In LO 3.6.7.2 there doesn't exist the possibility of "Print repeated values", only the possibility to "Print value on group change".
Have tested it a little bit more. You could choose this function in LO 4.1.6.2. If you set it to "Yes" the content of the field will be repeated all the time in the first group. So it didn't work right in this version, but it has an "effect". You couldn't choose this function in LO 4.0.5.2. So could be the button has been added to the report-builder in LO 4.1.0 It seems to be introduced with bug52948
** 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
Dear froilens, 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 https://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 appears also in LO 7.1.4.2 on OpenSUSE 15.2 64bit rpm Linux
Dear froilens, 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 https://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://web.libera.chat/?settings=#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
Bug still exists with LO 7.5.5.1 on OpenSUSE 15.4 64bit rpm Linux. Open the report odb69-Employee-Info+Phone1 for editing and set Detail → Group_Name → Print repeated values → Yes Detail → Group_Name → Print repeated value on group change → Yes Execute and you could see all Group_Name. Have a look at Emp-ID 9,10,11 and 15. All Group_names are the same as in the Emp-ID 8 and Emp-ID 14. Now switch Detail → Group_Name → Print repeated values → No There won't be shown any value for Group_Name n the group for Emp-ID 9,10,11 and 15 any more, but Print repeated value on group change → Yes is set.
Created attachment 194429 [details] screenshot of buggy report
This bug still exists in LO 7.6.5.2 (MacOS). It appears to be a duplicate of (or closely related to) bug 52948. At any rate, the bug still exists. The attached screenshot shows a report where for field "#Res" "Print repeated value on group change" is set to "Yes". The grouping is on "Address". Each line is a "detail". If I have "Print repeated values" set to "Yes", then I get the "2" repeated twice for the first address and twice for the second address. I would like it printed only once per address. However, when I do that, it doesn't get printed for the second address, ie, after the group has changed. The same is true for addresses 3 and 4, where there is only one resident per address. This bug seems to have been around forever, and nothing seems to have changed. My skills at programming are not good enough to try to weave through the code that is in reportdesign... Thanks for listening, and hopefully this bug can be squashed.