Created attachment 159822 [details] Contains the odt test document and sceenshots of good and buggy versions The table column sum-function does not work properly when there is a reference value of a number included in the summation ("Querverweis"). This occurs in Writer in some LibreOffice version after 6.0.0.3. At least, the problem occurs in the latest version 6.4.3.2 and the latest stable version before. I tested version 6.0.0.3 for good and started testing with the latest Open Office version 4.1.7. Also LibreOffice version 5.4.4.2 works well. All the previously noted versions show the same expected good behaviour: a referenced number value (of a "Querverweis") in the table column is treated like a number value directly entered into the summarized column. The value can have a thousands separator or not. The number format of the column can be currency too. In the latter case the Euro sign may not be part of the referenced number. You can change the value in the source of the referenced number ("Querverweis") und then refresh all using the Extras menu, so that the referenced value in the column sum is updated and the total sum too. This does not work in 6.4.3.2. Attached is a zip-file (LO test.zip) with screenshots and the test document (Test.odt) containing the table and the test environment.
reproducible with: Version: 6.2.8.2 (x64) Build-ID: f82ddfca21ebc1e222a662a32b25c0c9d20169ee CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; VCL: win; Gebietsschema: de-DE (de_DE); UI-Sprache: de-DE Calc: but *not* reproducible with: Version: 6.1.6.3 (x64) Build-ID: 5896ab1714085361c45cf540f76f60673dd96a72 CPU-Threads: 4; BS: Windows 10.0; UI-Render: Standard; Gebietsschema: de-DE (de_DE); Calc:
This seems to have started with: https://git.libreoffice.org/core/+/9336286a7ea5385541344f444e6f8702c85bdacb [API CHANGE] Resolves: tdf#42518 new KParseTokens::GROUP_SEPARATOR_IN_NUMBER Default unset bit now does not accept/skip group separators in numbers. See .idl description comment for why this is incompatible and how. This actually uncovered a "bug" (or at least unexpected) in the Math parser that parsed "0," as one entity instead of "0" followed by ",". As obtaining the text form appends a blank after each entity the sw/qa/extras/rtfexport/rtfexport.cxx testMathEqarray() testcase had to be adapted. /cygdrive/d/sources/bibisect/bibisect-win32-6.2 $ git bisect good c17fbd5031acd0c942669d81213488001c908769 is the first bad commit commit c17fbd5031acd0c942669d81213488001c908769 Author: Norbert Thiebaud <nthiebaud@gmail.com> Date: Sat Dec 1 09:26:31 2018 -0800 source 9336286a7ea5385541344f444e6f8702c85bdacb source 9336286a7ea5385541344f444e6f8702c85bdacb :040000 040000 2cbfc3490475a2d09b765a541beb7d00f577ffdd 36ef71b04bc2b480a549990b694f56d7dedca5a4 M instdir /cygdrive/d/sources/bibisect/bibisect-win32-6.2 $ git bisect log # bad: [32300ab0da959bbff1f09736ff655937319e7e3e] source 5f01fe15eb2661f1f9ce12d1d99dc2a705b462ee # good: [b0a56ec98b1368cb5e3e531e0b3f69565af91609] source 3a801799536e6870f2fb111b1cc00b9575a35a39 git bisect start 'master' 'oldest' # good: [696d8ce3656c1a7018e3647f381d01de8432cb19] source 43125f3b0b18b8d9bac9bd459fa234cb5ff9ddb4 git bisect good 696d8ce3656c1a7018e3647f381d01de8432cb19 # good: [313291982701f81331b6569203682bbb5da03ad9] source 922f935f9ddefcfc50d0bbf805c97ea3f9d5c5e6 git bisect good 313291982701f81331b6569203682bbb5da03ad9 # bad: [fa54824924d41aef8e5032a08cefde0a4c1d478b] source d3e4c06ccb3aa4bb9078077a49dc2b2795835a5c git bisect bad fa54824924d41aef8e5032a08cefde0a4c1d478b # good: [c75a7d7620be8cae959afe1d8b1540b2f25854a2] source d278f5cc5a239b6fed7b5a73917caa6d6473e5c6 git bisect good c75a7d7620be8cae959afe1d8b1540b2f25854a2 # bad: [3b78902da688a0163c5f6b8c3c7c524571580b4d] source 58fcd98bd0b66281c6c8a7b55054d8341c2da394 git bisect bad 3b78902da688a0163c5f6b8c3c7c524571580b4d # bad: [27bf7a137322bc6aaf82d0a6bf0e6edc84704762] source caf9cd9389b30cd6eb93735d89aae90c1d835f5c git bisect bad 27bf7a137322bc6aaf82d0a6bf0e6edc84704762 # good: [a5513e401c161e968b8a1bbf473e732379679f8f] source 5f8bae548fd84c26cd05af3563e6b6ba200edf74 git bisect good a5513e401c161e968b8a1bbf473e732379679f8f # good: [be33bfe12594d1ccbfded746ba62d03c28a9ff6f] source d197d524c5292cf6d66be802ec7d1fed78e30416 git bisect good be33bfe12594d1ccbfded746ba62d03c28a9ff6f # bad: [b24238e3ae2acfe1c2d9ab6ad83f6f6bf2021c96] source 525ed5d1fcb89412f0b80be0b1e35410b048c337 git bisect bad b24238e3ae2acfe1c2d9ab6ad83f6f6bf2021c96 # good: [fe088fc629f0d007651c950404ed1264b7efdec1] source 21c41659969cba4dc50d3208fb1736032c971661 git bisect good fe088fc629f0d007651c950404ed1264b7efdec1 # good: [077fe64ad3617f09bd5c7ef952cda7a29837ae32] source 0d3f1ed35a1f211d459b5da8eba83b404b2d8e31 git bisect good 077fe64ad3617f09bd5c7ef952cda7a29837ae32 # good: [94eecb1ddc570e0f8c253b2d48d415cca763d228] source 1d988778095ecbe84f1a1002511377d0708b3443 git bisect good 94eecb1ddc570e0f8c253b2d48d415cca763d228 # bad: [84f5ddce4b293c2961284547118c58cae5492633] source e22ab5e6f6b0ea49231ca454a567133996306116 git bisect bad 84f5ddce4b293c2961284547118c58cae5492633 # good: [fa9bfddba775b7d4fc68e63a169cda079b7dd640] source 973a3dd9623107c18c6765d0b247aa34018a0447 git bisect good fa9bfddba775b7d4fc68e63a169cda079b7dd640 # first bad commit: [84f5ddce4b293c2961284547118c58cae5492633] source e22ab5e6f6b0ea49231ca454a567133996306116 # bad: [32300ab0da959bbff1f09736ff655937319e7e3e] source 5f01fe15eb2661f1f9ce12d1d99dc2a705b462ee git bisect bad 32300ab0da959bbff1f09736ff655937319e7e3e # bad: [e42e8cbe4348b6caa89abe311142e799d34e5172] source 97803ae75c27368aa2880f58c0c661b9a01d4d00 git bisect bad e42e8cbe4348b6caa89abe311142e799d34e5172 # bad: [8edf18044c98a5588f92e9473eed8a9491f3527c] source c9de94c65b8ab8bf6073400eda5ba848ba22af47 git bisect bad 8edf18044c98a5588f92e9473eed8a9491f3527c # good: [b40a11222d02a05051692379bb9f9d427afe1bcf] source b39c91cf5a2c21924f8ac780dadab75a6a2a0713 git bisect good b40a11222d02a05051692379bb9f9d427afe1bcf # bad: [39d24ec1673f82081de5a3e97ce30d2411498157] source 9518a9af852f069a268badbc691abb4c09a37be8 git bisect bad 39d24ec1673f82081de5a3e97ce30d2411498157 # bad: [3ce778d06f8048982a68ff93ee4b18ce90386383] source 83afe755ba137f7cd572cb42afeff1a47a323dc6 git bisect bad 3ce778d06f8048982a68ff93ee4b18ce90386383 # bad: [02041b0a32abd81ffe6be824f53c5e4bb920ccfe] source 3f3c5dad9b41eb359fadf5aa81d4ed3f6dead46d git bisect bad 02041b0a32abd81ffe6be824f53c5e4bb920ccfe # good: [0f8fd5c6086277500cd87de3ee96b435e751f6e0] source 334a8dc379f28c084d2b07680ce3ae1f563651ef git bisect good 0f8fd5c6086277500cd87de3ee96b435e751f6e0 # good: [3b62ac6ad85864deb08e18af39ec802044e6972b] source bd4e761cde3d42dfa37501e7f0c49e94beb917bf git bisect good 3b62ac6ad85864deb08e18af39ec802044e6972b # good: [b3a597cbe399fa66281d5d6c73ad00029b4cecaf] source f52399177fcab220867c1dcae35c6db5c904138d git bisect good b3a597cbe399fa66281d5d6c73ad00029b4cecaf # bad: [c17fbd5031acd0c942669d81213488001c908769] source 9336286a7ea5385541344f444e6f8702c85bdacb git bisect bad c17fbd5031acd0c942669d81213488001c908769 # good: [8f6028efc3319237e74bdc7b79ba2ae588c69d70] source 4632afbd9ecdf85f3980b41fa9d58b6099aa2d81 git bisect good 8f6028efc3319237e74bdc7b79ba2ae588c69d70 # first bad commit: [c17fbd5031acd0c942669d81213488001c908769] source 9336286a7ea5385541344f444e6f8702c85bdacb
also reproducible with current LO 7.0 master. btw: It will work after removing the dot "." from "4.711,45" -> 4711,45 -> Menu Tools/Update/Update all
Created attachment 163478 [details] Extended and more detailed test on using separators in decimal number references I have made an extended and more detailed test on using separators in the value string of a reference number. Please read the summary in the test report first. I updated the title of the bug to make it correct. Test result: From the perspective of the test, the thousands separator has the least influence on the validity of the evaluation of decimal numbers. It is therefore a very unfortunate solution not to allow the use of the thousands separator in reference numbers in the table context, although the thousands separator improves the readability of numbers and therefore is widespread in everyday use. Therefore I will continue to use LibreOffice 6.1.0.3 and unfortunately not version 7.
REPRO in 7.4 Retested with Version: 7.4.0.0.alpha0+ / LibreOffice Community Build ID: 2f4f4cbeb8e50081d607b86b0475b93971c40ab8 CPU threads: 16; OS: Linux 5.13; UI render: default; VCL: gtk3 Locale: ro-RO (ro_RO.UTF-8); UI: en-US Calc: threaded
Dear Manfred, 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