Created attachment 122372 [details] unexpected changes occurs in sheet ID2 Some formulas that uses data from other sheets can change references unexpectedly if the source sheet cells has changed. I tried to find out if changes in references will go on other sheets but it didnt. for example if i have a connection like sheet1 -> sheet2 -> sheet3 then changeing some of data in sheet1 will sometime change references in sheet2 but sheet3 formulas using results in sheet2 will not change. But if i have only sheet2 (sheet1 -> sheet2) some changes in sheet1 will change some of references in sheet2. I use to change data within sheet1 by -copy/paste- not by -cut/paste- so i don't expect my formula references to be changed even if my formulas has no $ sing to lock reference of cell. I have to correct this changes manually if it occurs, also not all the formulas changes, only some of them.
Please Mehmet, could you attach a sample file as minimal as possible and the steps to reproduce the issue.
(In reply to m.a.riosv from comment #1) > Please Mehmet, could you attach a sample file as minimal as possible and the > steps to reproduce the issue. i have already attached the file that produces the problem i said. Problem occurs after some of changes made by <copy/paste> in sheet "GECE", not always but sometimes this changes cause -shift- some of the formulas in sheet "ID2". This changes affects several formulas within consecutive order in same column (for example W49---W58 or Z38--Z47). I can see the problem from unexpected results in sheet ID2 AJ5-AP19. Then i search for the error in rows lower than row25 and have to fix them bay <copy/past> the formulas from unaffected regions.
Sorry, but without a followed steps, it's no possible to find the issue. What do you copy/paste? and how do you do it?
Created attachment 122566 [details] a smaller file
(In reply to m.a.riosv from comment #3) > Sorry, but without a followed steps, it's no possible to find the issue. > > What do you copy/paste? and how do you do it? I finally figured out how this problem appears. The problem is about drag a region of information to another’s ones place by "mouse" drag. If both cells are referenced then references will follow moved data in new place, but reference to over written one will stay same. Accidentally making such a mistake cannot be completely fixed by < ctrl + Z >. Only the moved data will be undid, but the change in references will remain broken. Such an operation in msexcel will produce a warning for the cells to be overwritten and old references to overwritten cells will be broken with #REF info. In example with new attachment moving data in D4-D9 region to D8-D15 then undoing, and after this moving D20-D27 to D13-D20 then <undo> will produce severe destruction in referenced calculations in columns I,K,O, and Q. We have to fix these references manually.
Created attachment 122600 [details] Sample file modified. There is an option to show an overwrite warning: Menu/Tools/Options/LibreOffice calc/General First version with the issue undoing. Win10x64 Version: 4.2.8.2 Build Id.: 48d50dbfc06349262c9d50868e5c1f630a573ebd Attached last sample file, with a little modification to see better what is wrong, following the last reported steps-
After a new verification first version with the issue: Version: 4.2.0.0.beta1 Build Id: f4ca7b35f580827ad2c69ea6d29f7c9b48ebbac7 BTW hope 5.2 is used only for test purposes.
** Please read this message in its entirety before responding ** 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 on a currently supported version of LibreOffice (5.2.5 or 5.3.0 https://www.libreoffice.org/download/ If the bug is present, please leave a comment that includes the version of LibreOffice and your operating system, and any changes you see in the bug behavior If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a short comment that includes your version of LibreOffice and Operating System 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) http://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: http://webchat.freenode.net/?channels=libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug-20170306
Dear Mehmet Rıza Saraç, 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 http://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://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa Thank you for helping us make LibreOffice even better for everyone! Warm Regards, QA Team MassPing-UntouchedBug
In version 6.3.3 now undo can fix old references.
There is not patch to fix, so the proper it's resolved as works for me.