Bug 123073 - mail merge: conditional text followed by empty field not printed
Summary: mail merge: conditional text followed by empty field not printed
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Writer (show other bugs)
Version:
(earliest affected)
6.1.4.2 release
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Mail-Merge
  Show dependency treegraph
 
Reported: 2019-01-30 22:09 UTC by Ted Lee
Modified: 2019-12-10 16:06 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
small test database (four records, four fields each record) (4.59 KB, application/vnd.oasis.opendocument.database)
2019-01-30 22:09 UTC, Ted Lee
Details
label template (two lines — one field first line, two fields second line (18.83 KB, application/vnd.oasis.opendocument.text)
2019-01-30 22:11 UTC, Ted Lee
Details
result of mail merge (8.90 KB, application/vnd.oasis.opendocument.text)
2019-01-30 22:12 UTC, Ted Lee
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Ted Lee 2019-01-30 22:09:44 UTC
Created attachment 148779 [details]
small test database (four records, four fields each record)

Conditional text that should be printed (included) based on a database field followed by a database field that happens to by empty is not included.  Problem does not occur in 6.0 (which has a different problem that appears to have been reported) but occurs in 6.1.4.2 and all versions thereafter (including 6.3.0.0 alpha).  I do not know which version between 6.0 and 6.1.4.2 the problem arises in — haven't checked.  Attached are three documents:  a very small database, a label template, and the result of merging the db into the template. In short, the output should look something like

C1                     C2
field                  B



C3                      C4
                        field B


but what it produces (in the versions with the bug) is

C1                     C2
                       B



C3                      C4
                        field B

"field" is conditional text base on whether a particular db field is empty or not;
following ir is the field "B" which is "B" in some records and empty in others.

(1st attachment including with initial bug report; remaining two in later comments)
Comment 1 Ted Lee 2019-01-30 22:11:10 UTC
Created attachment 148780 [details]
label template (two lines — one field first line, two fields second line
Comment 2 Ted Lee 2019-01-30 22:12:37 UTC
Created attachment 148781 [details]
result of mail merge
Comment 3 Ted Lee 2019-01-30 22:14:57 UTC
Oops.  Mistyped in main comment:  earliest version I've found the bug in was 6.1.2.1.
Comment 4 Xisco Faulí 2019-06-10 16:52:32 UTC
Thank you for reporting the bug.
it seems you're using an old version of LibreOffice.
Could you please try to reproduce it with the latest version of LibreOffice
from https://www.libreoffice.org/download/libreoffice-fresh/ ?
I have set the bug's status to 'NEEDINFO'. Please change it back to
'UNCONFIRMED' if the bug is still present in the latest version.
Comment 5 QA Administrators 2019-12-09 03:40:12 UTC
Dear Ted Lee,

This bug has been in NEEDINFO status with no change for at least
6 months. Please provide the requested information as soon as
possible and mark the bug as UNCONFIRMED. Due to regular bug
tracker maintenance, if the bug is still in NEEDINFO status with
no change in 30 days the QA team will close the bug as INSUFFICIENTDATA
due to lack of needed information.

For more information about our NEEDINFO policy please read the
wiki located here:
https://wiki.documentfoundation.org/QA/Bugzilla/Fields/Status/NEEDINFO

If you have already provided the requested information, please
mark the bug as UNCONFIRMED so that the QA team knows that the
bug is ready to be confirmed.
 
Thank you for helping us make LibreOffice even better for everyone!

Warm Regards,
QA Team

MassPing-NeedInfo-Ping
Comment 6 Ted Lee 2019-12-09 04:13:25 UTC
Thanks for calling this to my attention.  I'll get the latest version of LO sometime in the next week or so and try to reproduce the problem.  I'll first start with the latest release version and if that is OK give the latest beta a try.
Comment 7 QA Administrators 2019-12-10 04:10:26 UTC
[Automated Action] NeedInfo-To-Unconfirmed
Comment 8 Xisco Faulí 2019-12-10 16:06:26 UTC
(In reply to Ted Lee from comment #6)
> Thanks for calling this to my attention.  I'll get the latest version of LO
> sometime in the next week or so and try to reproduce the problem.  I'll
> first start with the latest release version and if that is OK give the
> latest beta a try.

ok, looking forward to hearing from you next week