Bug 88179

Summary: Can't create reference for another spreadsheet's named cell
Product: LibreOffice Reporter: l
Component: SpreadsheetAssignee: Not Assigned <libreoffice-bugs>
Status: NEW --- QA Contact:
Severity: normal    
Priority: medium CC: raal
Version: 4.3.5.2 releaseKeywords: regression
Hardware: x86-64 (AMD64)   
OS: All   
Whiteboard: bibisectRequest
i915 platform: i915 features:
Attachments: the result of test steps

Description l 2015-01-07 20:23:27 UTC
Created attachment 111929 [details]
the result of test steps

I create a cell reference an other spreadsheet:
"='file:///C:/toReference.ods'#$namedCell.C7"
If I change the tab and cell reference to its name, like this:
"='file:///C:/toReference.ods'#toReference"
the cell display #NAME? error, and the cell formula change to:
"='file:///C:/toReference.ods'#file:///C:/toReference.ods"

Steps to reproduce:
1. Create a new spreadseet
2. Rename the first tab to "namedCell"
3. Enter "referenced data" string into C7 cell on namedCell tab
4. Add "toReferenceCell" name to C7 cell
5. Save the spreadseet as "toReference.ods"
6. Create an other spreadseet
7. Rename the first tab to "referencig"
8. Type "=" into B3 cell on referencig tab then click to C7 cell on namedCell tab in toReference.ods spreadseet.
9. Press Enter
10. The value of B3 cell will be: "='file:///C:/toReference.ods'#$namedCell.C7"
11. edit the value of B3 cell: chage the "$namedCell.C7" to "toReferenceCell"
12. Press Enter 


Current behavior:
B3 cell display "#NAME?" error and the formula change to: "='file:///C:/toReference.ods'#file:///C:/toReference.ods"

Expected behavior:
B3 cell display "toReferenceCell" string and the formula remain: "='file:///C:/toReference.ods'#toReferenceCell"
Comment 1 raal 2015-01-07 23:34:35 UTC
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

Unable to reproduce with LO 3.5 -> regression

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.