Bug 117374 - Mail merge skips a record
Summary: Mail merge skips a record
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
(earliest affected) release
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: Not Assigned
Depends on:
Blocks: Mail-Merge
  Show dependency treegraph
Reported: 2018-05-01 13:25 UTC by mark.g.j.christiaens
Modified: 2019-03-21 11:25 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:

Resulting merged file that has a missing label (9.19 KB, application/vnd.oasis.opendocument.text)
2018-05-01 13:26 UTC, mark.g.j.christiaens
Spreadsheet that is used as a database source (9.46 KB, application/vnd.oasis.opendocument.spreadsheet)
2018-05-01 13:27 UTC, mark.g.j.christiaens
Database that uses the spreadsheet as data source (2.10 KB, application/vnd.oasis.opendocument.database)
2018-05-01 13:27 UTC, mark.g.j.christiaens
Text document with labels that need to be merged with the database (13.67 KB, application/vnd.oasis.opendocument.text)
2018-05-01 13:28 UTC, mark.g.j.christiaens

Note You need to log in before you can comment on or make changes to this bug.
Description mark.g.j.christiaens 2018-05-01 13:25:59 UTC
I performed a mail merge to generate some labels and one of the labels is missing.

Steps to Reproduce:
1. Create a spreadsheet with 26 rows (and a heading)
2. Create a database that uses the spreadsheet as source data
3. Register the database
4. Create a document holding 24 labels.  In every label, insert some data base fields and a "next record" field to move forward to the next record in the database.
5. Print the document with labels.  LibreOffice will ask whether we want to do a mail merge.
6. Say yes and mail merge to a new ODT document

Actual Results:  
The result will be a ODT document that has labels for all the records in the spreadsheet except one: the label that should come right after the first page is skipped.

Expected Results:
All 26 labels should be generated.

Reproducible: Always

User Profile Reset: Yes

OpenGL enabled: Yes

Additional Info:

User-Agent: Mozilla/5.0 (X11; Fedora; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36
Comment 1 mark.g.j.christiaens 2018-05-01 13:26:55 UTC
Created attachment 141812 [details]
Resulting merged file that has a missing label
Comment 2 mark.g.j.christiaens 2018-05-01 13:27:23 UTC
Created attachment 141813 [details]
Spreadsheet that is used as a database source
Comment 3 mark.g.j.christiaens 2018-05-01 13:27:48 UTC
Created attachment 141814 [details]
Database that uses the spreadsheet as data source
Comment 4 mark.g.j.christiaens 2018-05-01 13:28:23 UTC
Created attachment 141815 [details]
Text document with labels that need to be merged with the database
Comment 5 Buovjaga 2018-06-07 17:08:24 UTC
Can you test with a daily appimage build? https://www.libreoffice.org/download/appimage
Just set the appimage file to be executable and run it.

Change back to UNCONFIRMED, if the problem persists. Change to RESOLVED WORKSFORME, if the problem went away.
Comment 6 QA Administrators 2019-01-11 15:23:01 UTC Comment hidden (obsolete)
Comment 7 QA Administrators 2019-03-21 11:25:59 UTC
Dear Bug Submitter,

Please read this message in its entirety before proceeding.

Your bug report is being closed as INSUFFICIENTDATA due to inactivity and
a lack of information which is needed in order to accurately
reproduce and confirm the problem. We encourage you to retest
your bug against the latest release. If the issue is still
present in the latest stable release, we need the following
information (please ignore any that you've already provided):

a) Provide details of your system including your operating
   system and the latest version of LibreOffice that you have
   confirmed the bug to be present

b) Provide easy to reproduce steps – the simpler the better

c) Provide any test case(s) which will help us confirm the problem

d) Provide screenshots of the problem if you think it might help

e) Read all comments and provide any requested information

Once all of this is done, please set the bug back to UNCONFIRMED
and we will attempt to reproduce the issue. Please do not:

a) respond via email 

b) update the version field in the bug or any of the other details
   on the top section of our bug tracker

Warm Regards,
QA Team