Created attachment 111659 [details] the file that contains the changed formulae In "test2.xlsx", there are formulae fetching data from a csv file "data2.csv" located in a different folder. After the file was saved and re-opened, the formulae changed to something like those reported in an already reported bug (https://bugs.freedesktop.org/show_bug.cgi?id=63992). Then, I tried to correct the formulae by deleting the extra parts. After the file was saved and re-opened again, the formulae changed to something like this: VLOOKUP(A2,[3]data2!a$1:B$20,2,0) That is, the path to the referenced file (data2.csv) has changed to [3].
Hello, is it duplicate of bug 76047?
I don't think they are the same. Take a look at this screenshot: http://imgbox.com/Fz3agg6H This is what I got after I saved the file and re-opened it. You can see that the path is something like 'file:///(path to this file)/(path to the referenced file) ...' The correct path should be simply 'file:///home/kenneth/downloads/data2.csv' Then, as I said in the report, I tried to correct the path by deleting the extra parts. I saved the file and re-opened it and now the formulae look like [3]data2.csv as shown in this screenshot: http://imgbox.com/1Y9jQ3xv
Your file is in xlsx format (test2.xlsx). Are you able to reproduce issue with .ods format (test2.ods)? Please attach .csv, I'll try to reproduce this.
Created attachment 111681 [details] The referenced csv file. the referenced csv file.
Seems that the ods format works fine. I now attach the csv file.
I can confirm with Version: 4.5.0.0.alpha0+ Build ID: 7f476fea47f06a7f8cc961dd4f6595a524346fa5 TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2014-12-27_23:36:28 steps to reproduce: - save csv file to /tmp - create xlsx file in /tmp/testBug - add formula to xlsx file =IF(B2=0;"";VLOOKUP(A2;'file:///tmp/data2.csv'#$data2.A1:B20;2;0)) - save as xlsx, close , reopen Actual results: formula changed to =IF(B2=0;"";VLOOKUP(A2;'file:///tmp/testBug/data2.csv'#$data2.A$1:B$20;2;0)) Expected results: formula unchanged
raal, What if you now in the re-opened file delete "testBug/" (without quotes, of course), save the file and re-open it again? Does the formula change?
(In reply to kenw from comment #7) > raal, > > What if you now in the re-opened file delete "testBug/" (without quotes, of > course), save the file and re-open it again? > > Does the formula change? formula will change =IF(B2=0;"";VLOOKUP(A2;[2]data2!a$1:B$20;2;0))
** 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.0.4 or later) 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 your help! -- The LibreOffice QA Team This NEW Message was generated on: 2016-01-17
** 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 kenw, 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
I checked this problem and still happens in: Version: 7.1.0.0.alpha0+ (x64) Build ID: f266feaebea39668392e3a3830e20e4670344658 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win Locale: hu-HU (hu_HU); UI: hu-HU Calc: CL I'll attach a bunch of reproducer documents in a zip: test2.ods: source file made in LO7.1alpha that contains a VLOOKUP function referencing XLSX and CSV files in the same directory (data3.csv and data3-copy.xlsx) and in a subdirectory (data2.csv and data2-copy.xlsx) as well. test2.xlsx: the above ods saved as XLSX. The VLOOKUP does not work in this one for the referenced files in the same directory, but works for the ones in the subdirectory. Excel 2013 reports invalid contents in this one and removes the formula with references to the same directory. test2-rel.ods: the above ods saved with Options - Load/Save - Save URLs relative to filesystem OFF. test2-rel.xlsx: test2-rel.ods saved to XLSX with Options - Load/Save - Save URLs relative to filesystem OFF. In this one all VLOOKUP functions work both in Calc/Excel.
Created attachment 166129 [details] Reproducer examples
Attila Szűcs committed a patch related to this issue. It has been pushed to "master": https://git.libreoffice.org/core/commit/f85d860ccbebd99bc128218148e2992c9415f221 tdf#87973 XLSX export: fix lost file names in modified links It will be available in 7.2.0. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
Attila Szűcs committed a patch related to this issue. It has been pushed to "libreoffice-7-1": https://git.libreoffice.org/core/commit/7050a83525a24f81b8c317716726e896210f314f tdf#87973 XLSX export: fix lost file names in modified links It will be available in 7.1.0.0.beta2. The patch should be included in the daily builds available at https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More information about daily builds can be found at: https://wiki.documentfoundation.org/Testing_Daily_Builds Affected users are encouraged to test the fix and report feedback.
*** Bug 126821 has been marked as a duplicate of this bug. ***