Bug 139405 - FILESAVE XLSX Named range with name S not allowed in Excel is saved to XLSX
Summary: FILESAVE XLSX Named range with name S not allowed in Excel is saved to XLSX
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:xlsx
Depends on:
Blocks: XLSX-Corrupted
  Show dependency treegraph
 
Reported: 2021-01-04 14:20 UTC by NISZ LibreOffice Team
Modified: 2023-03-19 03:25 UTC (History)
3 users (show)

See Also:
Crash report or crash signature:


Attachments
Minimized version of attachment #168418 (20.78 KB, application/vnd.oasis.opendocument.spreadsheet)
2021-01-04 14:20 UTC, NISZ LibreOffice Team
Details
The original file saved by Calc (13.75 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2021-01-04 14:20 UTC, NISZ LibreOffice Team
Details
Screenshot of the exported document side by side in Excel and Calc (108.37 KB, image/png)
2021-01-04 14:20 UTC, NISZ LibreOffice Team
Details
Error message from Excel when creating a new named range named “S” (47.64 KB, image/png)
2021-01-04 14:23 UTC, NISZ LibreOffice Team
Details

Note You need to log in before you can comment on or make changes to this bug.
Description NISZ LibreOffice Team 2021-01-04 14:20:11 UTC
Created attachment 168667 [details]
Minimized version of attachment #168418 [details]

This is split off from bug #139163
There the ODS attachment #168418 [details] has several named ranges, saving them to XLSX makes Excel find invalid contents in the named ranges.
The cause seems to be the named range “S” which is not allowed in Excel, can not even be created as new.
Removing only this one from the Manage names dialog makes the error go away.

Steps to reproduce:
    1. Open attached file
    2. Save as XLSX, reopen in Excel
       
    3. For a counter-test open attachment #168418 [details]
    4. In the Manage Names dialog find and delete the named range “S”
    5. Save as XLSX, reopen in Excel -> no invalid contents error among named ranges.

Actual results:
Excel finds invalid contents.

Expected results:
No invalid contents.

LibreOffice details:
Version: 7.2.0.0.alpha0+ (x64)
Build ID: 96bafa464ebdbce3ef04bec9beae5e745bb37794
CPU threads: 4; OS: Windows 6.3 Build 9600; UI render: Skia/Raster; VCL: win
Locale: en-US (hu_HU); UI: en-US
Calc: CL

Also with 6.0, 5.0, 4.0. Also happens when saving to XLS format.
Comment 1 NISZ LibreOffice Team 2021-01-04 14:20:30 UTC
Created attachment 168668 [details]
The original file saved by Calc
Comment 2 NISZ LibreOffice Team 2021-01-04 14:20:46 UTC
Created attachment 168669 [details]
Screenshot of the exported document side by side in Excel and Calc
Comment 3 NISZ LibreOffice Team 2021-01-04 14:23:03 UTC
Created attachment 168670 [details]
Error message from Excel when creating a new named range named “S”

This says even with a new spreadsheet:
- The name does not start with letter or underscore.
- The name contains space or another invalid character.
- The name clashes with a built-in name of Excel or with the name of another object of the spreadsheet.
Comment 4 Xisco Faulí 2021-02-23 09:40:24 UTC
I can't reproduce it in

Version: 7.2.0.0.alpha0+ / LibreOffice Community
Build ID: a1d987cf3d0e1ae4d87f7d06ae93e71a0cc59f0c
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 Excel 2010.
Which version of Excel are you using? might it be a problem in that version of excel ?
Comment 5 NISZ LibreOffice Team 2021-03-11 13:37:03 UTC
(In reply to Xisco Faulí from comment #4)
> I can't reproduce it in
> 
> Version: 7.2.0.0.alpha0+ / LibreOffice Community
> Build ID: a1d987cf3d0e1ae4d87f7d06ae93e71a0cc59f0c
> 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 Excel 2010.
> Which version of Excel are you using? might it be a problem in that version
> of excel ?

I used 2013, now they upgraded my machine to 2019 but it also does not like the named range in the minimized file.
Comment 6 Xisco Faulí 2021-03-18 17:36:20 UTC
let's move it to NEW then...
Comment 7 QA Administrators 2023-03-19 03:25:42 UTC
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