Created attachment 122156 [details] Merged individual document for first record Overview : when using "Mail Merge Wizard" to save merged documents, every records from the database is written in merged individual documents. Steps to reproduce : Prerequisite : a database registered 1. Tools -> "Mail Merge Wizard" 2. Select step 3 : "Insert address block" 3. Click on "Select Different Address List..." button 4. Select the previously registered database and click "Ok" 5. Select step 6 : "Edit document" 6. Click on "Edit Document..." button 7. Click on Insert -> Header -> Default Style 8. In the header, click on Insert -> Fields -> Other... -> Database 9. Add fields from the previously registered database (inside the header) 10. Close the "Fields" window 11. Click on "Return to Mail Merge Wizard" 12. Select step 8 : "Save, print or send" 13. Select "Save merged document" and "Save as individual documents" 14. Click on "Save Documents" button 15. Choose a name and select a folder. Click on save Actual Results : The merged documents are generated but styles.xml files of each generated file contains every records from the database Expected Results : The merged documents are generated. styles.xml files of each generated file doesn't contain the whole database. Date & Hardware : 2016-01-22 on Debian Jessie x64 (LibO 4.3.3.2) Additional platform : Windows 7 Pro x64 (Lib0 4.4.7.2)
Before testers give it a shot, could you please test with LibreOffice 5.1? http://www.libreoffice.org/download/pre-releases/ https://wiki.documentfoundation.org/Installing_in_parallel Set to NEEDINFO. Change back to UNCONFIRMED, if the problem persists in 5.1. Change to RESOLVED WORKSFORME, if the problem went away. If the problem persists in 5.1, attaching example files would be good so testers can always test as quickly as possible.
In SwMailMergeOutputPage::SaveOutputHdl_Impl the single documents are copied from the mail merge result file. Unused page styles should be removed here.
(In reply to Buovjaga from comment #1) > Before testers give it a shot, could you please test with LibreOffice 5.1? > http://www.libreoffice.org/download/pre-releases/ > https://wiki.documentfoundation.org/Installing_in_parallel > > Set to NEEDINFO. > Change back to UNCONFIRMED, if the problem persists in 5.1. Change to > RESOLVED WORKSFORME, if the problem went away. > > If the problem persists in 5.1, attaching example files would be good so > testers can always test as quickly as possible. I have just tested with LibO 5.1.1.3 (x64) Build ID: 89f508ef3ecebd2cfb8e1def0f0ba9a803b88a6d (OS : Windows 10 pro x64). Same problem. (see Attachment 122156 [details] )
** 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
Still reproducible with current master. A potential fix for review: https://gerrit.libreoffice.org/#/c/81095/
(In reply to Michael Weghorn from comment #5) > Still reproducible with current master. > > A potential fix for review: https://gerrit.libreoffice.org/#/c/81095/ As mentioned in the Gerrit patch, this needs some further investigation, but I don't really get to that currently. I'm unassigning for now; if anybody else wants to take over, please do.
Dear spamici, 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