Description: DEFINED table formula has Expression is faulty when opened in LO. Steps to Reproduce: 1. Create a new docx in Word. 2. Insert a Table. 3. Insert DEFINED() formula to some of the cells. 4. Save and open it in LO. Actual Results: The cells which had and DEFINED formula now have ** Expression is faulty ** instead of what was in them in Word. Expected Results: All the cells should have the same data in them. Reproducible: Always User Profile Reset: No Additional Info: LibreOffice details: Version: 6.3.0.0.alpha0+ Build ID: 17dd2662ccfa9d04efbea74e5d7548db5b2126d4 CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; Locale: hu-HU (hu_HU); UI-Language: en-US Calc: threaded
Created attachment 149155 [details] Screenshot of the original document side by side in Word and Writer.
Created attachment 149156 [details] Document with DEFINED table formulas.
Regression introduced by: https://cgit.freedesktop.org/libreoffice/core/commit/?id=c568eb7d3bb4584867f0a1f0a7965f73097f009b author Jean-Sebastien Bevilacqua <realitix@gmail.com> 2017-02-16 09:54:33 (GMT) committer Miklos Vajna <vmiklos@collabora.co.uk> 2017-03-30 17:39:00 (GMT) commit c568eb7d3bb4584867f0a1f0a7965f73097f009b (patch) tree ea7e6fb1e0d77369a90bc69dd8756f589bb352e4 parent 53c2507bf97867011fd2bfbbac6c86b7fc494338 (diff) tdf#105975 Add Formula field parsing (docx) in SWriter Introduction Bisected with bibisect-linux-64-5.4 Adding Cc: to Jean-Sebastien Bevilacqua
Formula: debug:6656:6656: =DEFINED(test_argument)
Repro 7.1+
Still reproducible in Version: 7.2.0.0.alpha0+ Build ID: 84af20ef3ea72190784e9e7be820684c2558ba8c CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded
Dear NISZ LibreOffice Team, 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