I've found a display bug in the document preview of the mail merge assistant.
Steps to reproduce:
1. create a document
2. link a spreadsheet as database
3. insert database fields
4. create a conditional text with following condition
4.1 condition: [title] != ""
4.2 then: " "
4.3 else: ""
5. use mail merge assistant and click through the setting until document preview
6. scroll through the previewed data (filled fields) if the condition would be false the empty field is suppressed but the conditional whitespace is still in preview.
If I print/save the mail merge document, all fields and conditional text are handled correctly. So I think this is just a bug of the document preview of mail merge which does not solve the condition properly.
In my case I wanted to display just a whitespace if there is a title (academic grade) to print for the address field.
Please provide test document and datasource for us to try and reproduce. Not all of us are db experts or mailmerge pros.
In addition, what you don't specify, but is implied, is that your datasource has a field called title, for which some of the records are empty in the spreadsheet. This kind of implicit omission makes it harder for inexperienced mailmerge/db Qaers to try and reproduce the buggy behaviour.
Setting to NEEDINFO pending requested information. pLease set back to UNCONFIRMED once you have provided it.
Created attachment 113838 [details]
document template, calc sheet, database and printed mil merge document
sure, I've wrapped all needed data to the attached zip archive.
the screenshot shows the behavior if the conditional text (whitespace) is not calculated correctly by the mail merge assistant.
The test-letter.odt is the printed mail merge document to show, that after printing the document, the conditional text ist calculated correctly.
the database can be used to register with LO for mail merge assistant.
Hope there are all needed infos. :)
Build ID: 34d6ec2c6e6618beacac881ec28ab527b25558d1
when the document preview is displayed, the added whitespace is visible, however, this is not so in the final document (which is correct), so the preview is wrong.
Can someone please veryfy, if my fix for the regression for bug 70346 fixed your problem?
** 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)
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
Had some trouble understanding how to test this (how to get the preview), but think I figured it out in the end.
Comparing 188.8.131.52 with current master, there is no space before Max, so this works for me
Build ID: a488c7ad2763b944713997911c1ddb0315d8c93f
CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default;
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-03-26_00:38:29
Locale: en-US (en_US.UTF-8); Calc: group