Bug 156771 - Mail Merge create fails to include all lines with fields
Summary: Mail Merge create fails to include all lines with fields
Status: RESOLVED INSUFFICIENTDATA
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
24.2.0.0 alpha0+
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-08-14 18:16 UTC by Erik Fjerstad
Modified: 2025-11-25 15:34 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Zip file containing test files, instructions, and description of the bug. (134.43 KB, application/x-zip-compressed)
2023-08-15 21:08 UTC, Erik Fjerstad
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Erik Fjerstad 2023-08-14 18:16:54 UTC
Description:
With 24.2.0.0.alpha0+ (X86_64) / Build ID: 256d5fe2e7cb1bb002d5fe59527d3a3fbf6963f
Mail merge to a text file fails to include some lines, usually with fields that have no data (a blank cell in the db), also fails to include last line in field area.  Also different results between merge to email vs merge to file.  Previous versions (don't recall which ones) worked properly.  Open Office writer works properly with same files.

Steps to Reproduce:
1. Create db that has cells with no data
2. create .odt with lines that have cell description (title) and then field
3. Create email or create file, observe results with some missing lines.

Actual Results:
(Output From Libre Office Dev)
Primary lease holder for the specific hangar:    <New Info:          >

Thanks for your help in this project!

Expected Results:
(Output from Open Office Writer. Note 2 lines of text here missing from above)
Primary lease holder for the specific hangar:    <New Info:          >
Master Lease Holder (direct to TAA):   <New Info:          >
Remarks:   <New Info:          >

Thanks for your help in this project!


Reproducible: Always


User Profile Reset: Yes

Additional Info:
I believe this was working on earlier versions of the dev build, but I do not have records of which one.  The old "open office" worked as expected.
Comment 1 m_a_riosv 2023-08-15 00:46:54 UTC
Please attach the needed sample files.
Comment 2 Erik Fjerstad 2023-08-15 21:08:40 UTC
Created attachment 188987 [details]
Zip file containing test files, instructions, and description of the bug.

Actual database has proprietary and personal info.  Created test database that successfully shows the bug.  Zip file contains a description file and the necessary test input and output files:  .ods, .odb, .odt inputs as well as the .odt output with evidence of the bug.  Also included is the build info on the sw.
Comment 3 QA Administrators 2023-08-17 03:19:31 UTC Comment hidden (obsolete)
Comment 4 Dieter 2024-10-24 12:51:47 UTC
Erik, it seems, that nobody could confirm the problem for more than a year. Is it still reproducible for you with actual version LO 24.8?
=> NEEDINFO
Comment 5 QA Administrators 2025-04-23 03:10:35 UTC Comment hidden (obsolete)
Comment 6 QA Administrators 2025-11-25 15:34:45 UTC
Dear Erik Fjerstad,

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

MassPing-NeedInfo-FollowUp