Created attachment 166827 [details] Data source file with data table from Excel Attached Excel-made example file contains a data table with month names and a named range with month names. Other file ha defined names referencing the data table and the named range, then using these in VLOOKUP functions. When opened in Calc the file name of the data table referencing defined name is not resolved as can be seen in the Manage Names dialog, and the VLOOKUP using them gives Err:501 error. The simple defined name works fine. Steps to reproduce: 1. Open attached files in Calc Actual results: Err:501 errors in column C, unresolved file name in the Manage Names dialog. Expected results: File name resolved in Manage Names dialog, VLOOKUP works like in Excel. LibreOffice details: Version: 7.1.0.0.alpha1+ (x64) Build ID: f27c4ec5c864395f4cdaec32d7e95ff24e4f43c8 CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: default; VCL: win Locale: hu-HU (hu_HU); UI: en-US Calc: CL
Created attachment 166828 [details] Example file with defined name referencing the data table and named range in the other file.
Created attachment 166829 [details] Screenshot of the original document side by side in Excel and Calc
Reproduced in Version: 7.1.0.0.alpha1+ Build ID: 9c8ed8c8526b9b696d0bf592eb7d963950f3cef4 CPU threads: 4; OS: Linux 5.7; UI render: default; VCL: gtk3 Locale: en-US (en_US.UTF-8); UI: en-US Calc: threaded and Version: 5.2.0.0.alpha0+ Build ID: 13d4398820ded5914f635757865e258db2db2b57 CPU Threads: 4; OS Version: Linux 5.7; UI Render: default; Locale: en-US (en_US.UTF-8)
@Eike, this is another name range related issue, I thought you might be interested
Also reproduced in Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)
Maybe I found bug 116331 again... but let's keep this open just in case.
Dear NISZ LibreOffice Team, 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