Bug 150733 - Incorrect data with FILESAVE to XLSX when using EDATE function and opened with MSO2016
Summary: Incorrect data with FILESAVE to XLSX when using EDATE function and opened wit...
Status: CLOSED DUPLICATE of bug 142293
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
7.4.0.3 release
Hardware: x86-64 (AMD64) Windows (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-08-31 20:21 UTC by Eric
Modified: 2022-08-31 21:43 UTC (History)
0 users

See Also:
Crash report or crash signature:


Attachments
XLSX displaying incorrect data in cell A2 when opened with MSO2016 (4.80 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2022-08-31 20:24 UTC, Eric
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Eric 2022-08-31 20:21:13 UTC
Description:
After saving an XLSX file in MSO2016 using the EDATE function, opening the same file in LibreOffice Calc, saving the file as XLSX again, then opening the file in MSO2016 results it incorrect data.

Steps to Reproduce:
1.Open a new sheet in MSO2016 Excel
2.Fill cell A1 with =TODAY()
3.Fill cell A2 with =EDATE(A1,-24)
4.Format both cells as Date 3/14/2012 format
5.Save the file in the XLSX file format
6.Open the file with LibreOffice
7.Save the file in the .xlsx file format
7.Open the XLSX file in MSO2016 Excel

Actual Results:
The output in cell A2 shows #NAME?
Clicking on the cell reveals the function has changed to =com.sun.star.sheet.addin.Analysis.getEdate(A1,-24)

Expected Results:
The output in cell A2 should show today's date minus 2 years.


Reproducible: Always


User Profile Reset: Yes


OpenGL enabled: Yes

Additional Info:
Version: 7.4.0.3 (x64) / LibreOffice Community
Build ID: f85e47c08ddd19c015c0114a68350214f7066f5a
CPU threads: 12; OS: Windows 10.0 Build 19044; UI render: Skia/Raster; VCL: win
Locale: en-US (en_US); UI: en-US
Calc: CL

Microsoft® Excel® 2016 MSO (Version 2207 Build 16.0.15427.20166) 32-bit

Renderer: AMD Radeon(TM) Graphics
Vendor: ATI Technologies Inc.
Version: 4.6.14800 Core Profile Forward-Compatible Context 22.5.1 30.0.15021.11005
Shading language version: 4.60
Comment 1 Eric 2022-08-31 20:24:24 UTC
Created attachment 182126 [details]
XLSX displaying incorrect data in cell A2 when opened with MSO2016
Comment 2 Eike Rathke 2022-08-31 21:15:59 UTC
Closing as duplicate (though that other bug is intermixed with a Turkish locale peculiarity), but we still don't know what the exact circumstances are that would lead to the internal programmatic name being saved instead of the proper function name. So if you could contribute any knowledge that would enlighten this that would be welcome. Unfortunately the file attached here is already the erroneous one. Could you attach the original Excel file to bug 142293 please? Thanks.

*** This bug has been marked as a duplicate of bug 142293 ***
Comment 3 Eike Rathke 2022-08-31 21:43:09 UTC
Forget it, I can reproduce now. Thanks anyway.