Created attachment 180902 [details] Example file from Word 2016 with Mail Merge fields as IF field conditions This is a followup to bug 149660 In Word it is possible to use Mail Merge fields as conditions of the IF field, by the Mailings ribbon - Rules - If ... Then ... Else dropdown menu. This causes the IF field to be evaluated based on values in the data source. Using data source fields as conditions in IF fields is supported in Writer, but the docx import of these fields is likely missing. 1, Open attached document, and import the data source xlsx file too 2, The Mail merge toolbar should be able to step through the data source data points, and the value of the IF fields should change accordingly. Version: 7.5.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 3b852f274696a5e2a44bb4107c37cea9d291758e CPU threads: 14; OS: Windows 10.0 Build 19044; UI render: default; VCL: win Locale: en-US (hu_HU); UI: en-US Calc: threaded
Created attachment 180903 [details] Example data source
Gabor, since there seems to be nobody who could (or tried9 to confirm the bug, I would try to do it, but steps are too raw for me. I've opened test fle, but don't know how to import data source.
File - New - Database - Connect to an existing database - Spreadsheet. It will be registered by default. View - Toolbars - Mail merge If I click the Next Mail Merge Entry in the toolbar, four paragraphs get cleared. I guess this confirms the issue. Arch Linux 64-bit, X11 Version: 7.6.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 0d8d0fb8932652f182c46805d5cf3ae7f6ebadd5 CPU threads: 8; OS: Linux 6.2; UI render: default; VCL: kf5 (cairo+xcb) Locale: fi-FI (fi_FI.UTF-8); UI: en-US Calc: threaded Built on 16 March 2023
Dear Gabor Kelemen (allotropia), 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