Bug 76709 - Err:520 when using external link in ods format
Summary: Err:520 when using external link in ods format
Status: NEEDINFO
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Spreadsheet (show other bugs)
Version: 4.2.1.1 release
Hardware: x86 (IA32) Windows (All)
: medium normal
Assignee: Not Assigned
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2014-03-27 21:08 UTC by Mike B
Modified: 2014-08-21 06:36 UTC (History)
2 users (show)

See Also:
i915 platform:
i915 features:


Attachments
sample monthly file with all irrelevant pages cleared (35.37 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-27 21:08 UTC, Mike B
Details
sample stocks file for linkage testing (26.92 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-27 21:09 UTC, Mike B
Details
sample monthly file reuploaded to correct MIME type (35.37 KB, application/vnd.oasis.opendocument.spreadsheet)
2014-03-27 21:11 UTC, Mike B
Details

Description Mike B 2014-03-27 21:08:56 UTC
Created attachment 96487 [details]
sample monthly file with all irrelevant pages cleared

Multi-page spreadsheets. Reference in one spreadsheet to a page and cell in an external (closed) spreadsheet fails in one cell with "Err:520" shown. Other cells with similar references work. 

If other cells are changed to refer to the target page/cell in the external file they work. 
If the failing cell is COPIED to another cell and adjusted to refer to the correct page there, it will initially work but later fail.
If the cell is changed, file saved, then edited to refer to the correct external page/cell again, the correct value will appear but will again fail after the external links are refreshed either manually (Edit-Links-Update) or by save/close and reopen with external links updated.
If the target spreadsheet is open, all links work. 

** If the name of the source spreadsheet (where the failing cell is located) is changed so that the name includes more than just the month and year (say, MAR2014.ODS change to MAR2014C.ODS) all links work. 

Dependency seems to exist between the name of the open file and behavior of one cell in the file?

File setup is, in an annual directory:
Month files:  JAN2014.ODS, FEB2014.ODS, MAR2014.ODS ...
Stock records file:  STOCKS14.ODS

Failure first noted in 4.2.1.1 release; 4.2.2.1 not tested
Failure also occurs in LO 4.1.5.3 release (currently in use)
Not been tested in 4.0
Worked correctly in 3.6.5.2 release

Attachment is the first of 2 files. Will add the external link file afterward.
The failure is in the monthly file, in the cell referring to the external stocks file for the number of shares for IBM. CVX reference always works correctly.

Note: the sample files don't appear to have the problem. No idea why. But they do contain the linkage examples that have the problem.

Workaround: will be changing filenames and/or directory names, but that's a lot of editing ... or building batch files to always open both the monthly and the stocks file for every editing session.
Comment 1 Mike B 2014-03-27 21:09:43 UTC
Created attachment 96488 [details]
sample stocks file for linkage testing
Comment 2 Mike B 2014-03-27 21:11:20 UTC
Created attachment 96489 [details]
sample monthly file reuploaded to correct MIME type
Comment 3 Mike B 2014-03-27 21:12:17 UTC
Comment on attachment 96487 [details]
sample monthly file with all irrelevant pages cleared

Incorrect MIME type detected. See reupload.
Comment 4 Mike B 2014-04-17 21:30:56 UTC
In one other case, I triggered a 'Err:520' by accidentally entering an invalid character ("!") into a file name in a similar external-reference cell - permanently fixed by fixing the file name. The file name is correct in the one triggering the error described here, however.
Comment 5 raal 2014-08-21 06:36:12 UTC
Hello Mike,
I opened both of your files  and doesn't see any 'Err:520'. Please, where you see 'Err:520' in your files (column H,file "stock")? Thank you
	
Tested with LO version 4.2.4.2, Linux; Version: 4.3.0.4, Windows 7


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.