Created attachment 192358 [details] Example file from Writer When a table row that is referenced in a table function is deleted, the function is updated in an invalid way. 1. Open attached document 2. From the first table delete the first or second row -> the SUM formula in the third row becomes invalid, such as SUM<B1:?> 3. From the third table delete the second row -> the SUM formula in the fourth row is still valid, changes from SUM<B1:B3> to SUM<B1:B3> Deleting one more row would make this invalid as well. Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: dfcdef6d94993131b5f150d00d08cc81a987eebb CPU threads: 15; OS: Windows 10.0 Build 19045; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: threaded already in LO 3.3.
Created attachment 192359 [details] Screenshot of the broken formula
It works the same as it does in Calc. Deleting the first or last row (cell) of a range broke the range. But deleting some row (cell) inside the range doesn't, the range is reduced, to adapt the last row (cell) to the new range. In the second case, the new range is B1:B2 instead B1:B3. I think there is not a bug. Tested with Version: 24.2.1.0.0+ (X86_64) / LibreOffice Community Build ID: cafcc50570f9edaaebe74d2152bae5df1cc2edfe CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Raster; VCL: win Locale: es-ES (es_ES); UI: en-US Calc: CL threaded + Version: 24.8.0.0.alpha0+ (X86_64) / LibreOffice Community Build ID: 1647493e5cbb9cf4f06b7d0387d6763a2f30fdae CPU threads: 16; OS: Windows 10.0 Build 22631; UI render: Skia/Vulkan; VCL: win Locale: es-ES (es_ES); UI: es-ES Calc: CL threaded
(In reply to m_a_riosv from comment #2) > It works the same as it does in Calc. I don't see the same in Calc: first or last row deletion does not make a sum formula invalid, the range is updated as OP expects. I agree that how Writer behaves currently is not expected nor elegant. The range should be updated and the formula still valid.
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