Description: In Libre Office help for defining conditions for database fileds, NOT Database.Table.Company & Database.Table.Company EQ "" are considered equivalent. That is true for single fileds but I have found that for 2 or more fields, that is not true. Steps to Reproduce: 1.Insert a section in a writer for mail merge. 2.Insert more than one mail merge field in the section 3.Edit the section to hide it if any of the fileds are missing 4.Enter [Database.Table.Field1]EQ "" OR [Database.Table.Field2] EQ "" Actual Results: If Database.Table.Field1 OR Database.Table.Field2 is missing, the section is not not hidden. Expected Results: If Database.Table.Field1 OR Database.Table.Field2 is missing, the section should be hidden. Reproducible: Always User Profile Reset: No Additional Info: I have found that if I change the code to: NOT[Database.Table.Field1] OR NOT [Database.Table.Field2] and either filed is missing, the section is hidden as expected. Although EQ "" works for single fields, in this case, it does not work.
Could confirm [Database.Table.Field1] EQ "" OR [Database.Table.Field2] EQ "" won't hide anything in a section. [Database.Table.Field1] EQ "" will hide content, if there is no entry in Field1 NOT [Database.Table.Field1] OR NOT [Database.Table.Field2] will hide content, if there is no entry in Field1 or Field2. Tested with OpenSUSE 15.3 64bit rpm Linux Version: 7.5.0.2 (X86_64) / LibreOffice Community Build ID: c0dd1bc3f1a385d110b88e26ece634da94921f58 CPU threads: 6; OS: Linux 5.3; UI render: default; VCL: kf5 (cairo+xcb) Locale: de-DE (de_DE.UTF-8); UI: en-US Calc: threaded It's the same behavior here in every version I have installed, also LO 5.1.5.2 Might be it has been inherited by OOo. Has been reported for Windows, here for Linux.
Thanks Robert, your confirmaton is greatly appreciated! Souldn't the "LibreOffice Help" section be revised?
Dear Nick, 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