Created attachment 113561 [details] Tarball of document and data source. When changing the data source for a mail merge, even after deleting all references to the previous data source, printing the doc seems to always print one record per page, with each copy shown, rather than just printing one cell for each, as it does before the data source change.
If you would like, I can produce a video of the behavior.
(In reply to Jesse Gumm from comment #1) > If you would like, I can produce a video of the behavior. Hi Jesse, I believe that the 4.2 branch is EOL or about to be EOL. Can you reproduce the problem with one of our latest builds, e.g. 4.4.0.3? https://www.libreoffice.org/download/ Status -> NEEDINFO
Thanks. Just installed 4.4.1.2 from chttps://launchpad.net/~libreoffice/+archive/ubuntu/ppa The behaviour still exists. I've produced a simple video demonstrating: http://youtu.be/lMVhBkAU6To In this video, I have a LibreOffice Calc sheet with 80 records. I expect simply reassigning the fields to the new data source to properly remap, but instead something seems to go wonky and instead of printing 80 records, it prints 80 *pages*, with 10 on each page.
(In reply to Jesse Gumm from comment #0) > Created attachment 113561 [details] > Tarball of document and data source. It seems you forgot to include the .ods (I tried printing and it failed complaining about the missing .ods).
Created attachment 113753 [details] Updated tarball with ods file
Indeed. My apologies, I had assumed the .odb file was a self-contained database, rather than a reference to the original .ods file. I've uploaded a new tarball with the source document and .ods file (I've also removed the .odb file, as it's not necessary to reproduce). Further, using those two files, I've uploaded a reproduction video demonstrating the exact process I use to reproduce the issue (http://youtu.be/sr7QofmSnuI). Thanks.
(In reply to Jesse Gumm from comment #6) > Further, using those two files, I've uploaded a reproduction video > demonstrating the exact process I use to reproduce the issue > (http://youtu.be/sr7QofmSnuI). 1. Open Hazard Card Print.odt 2. Right-click name field in first cell, select Fields 3. Add alien board game.ods 4. In alien board game, expand table Hazard cards and select field name 5. Click Synchronize labels 6. Print (click yes) Unfortunately, I have no idea, how it should look, which is wrong and which is right. I'm setting to NEW anyways and attaching a printed PDF. Win 7 Pro 64-bit, LibO Version: 4.4.1.2 Build ID: 45e2de17089c24a1fa810c8f975a7171ba4cd432 Locale: fi_FI
Created attachment 113756 [details] PDF printed from 4.4.1 Win 7 The first cell in every page is missing the name field, which is not what is shown in the Youtube video preview.
Thank you, you've correctly reproduced it (though why the name field is missing from the first record on each in your printoff is a mystery to me). I'm attaching the file I use now that works, but I hesitate to make any changes to it, or connect it to a different source, for fear that it will once again exhibit this behavior. But each record from the spreadsheet is expected to show only once, producing a 2-page printoff, rather than an 18-page printoff.
Created attachment 113757 [details] Expected Look of the printoff
Please note, that the expected printoff doesn't look "exactly" like the original, because the only solution I could find was recreate it completely, starting from scratch (File > New > Labels, etc), so it has some differences. The takeaway is that it should be a single record per cell, rather than the rendering single-record-per-page.
** 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.5 or 5.1.2 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-04-16
Reverting incorrect status change.
** 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
Probably I have a similar situation. A year ago I successfully printed labels using Libreoffice. Now I tried again and cannot arrive at the desired result. The label sheet is different now. The table holding the Database is also a different one and the Libreoffice version is different too. I am running now Ubuntu 20.04.2 LTS, LibreOffice Version: 6.4.6.2. I attach the writer document created. When I open Etiketten5*13.odt everything looks good. An entire page is filled with 13 rows of labels and in each row there are 5 labels. All but the first one are write protected and filled/updated using sync. Each label holds two paragraphs: The first § holds Database element <L11> and a small image aligned left. The second § holds the string *<L11>* the same Database element preceded by a start character * and ending and terminating in a stop character *. This § is using a code3of9 barcode font I attach also the HGV-FG_label02.ods document holding table F_Mrz2021-1 with 440 lines and header line. When I try to print the labels a pop-up informs me that "Your document contains database fields. Do you wand to print a form letter?". I can choose yes or no. When I chose "no" one page is printed with all labels showing the database reference <L11>, the small image and *<L11>* translated to barcode. I think that is ok. However when I chose "yes" I have to wait quit a while. 440 pages are generated each one of the 65 labels on the page filled with identical labels. The first page has all the Database fields filled with the value in the first line of column L11, The second page uses the value in line 2 and so on. The last page uses the value in line 440. This is definitely not the result I want.
Created attachment 171200 [details] contains table F_Mrz2021
Created attachment 171201 [details] label sheet
Repro OO and LO 7.4+ for original sample. Doesn't have to be printed, wrong result seen with > on Mail Merge Toolbar.
Dear Jesse Gumm, 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