Bug 122715 - FILEOPEN XLSB format is inconsistent with Excel with incorrect cell references and hiding
Summary: FILEOPEN XLSB format is inconsistent with Excel with incorrect cell reference...
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
  Show dependency treegraph
 
Reported: 2019-01-14 20:25 UTC by byronigoe
Modified: 2025-05-29 03:12 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Illustrates the bug (58.65 KB, application/vnd.ms-excel.sheet.binary.macroEnabled.12)
2019-01-14 20:27 UTC, byronigoe
Details
comparison MSO 2010 and LibreOffice 6.3 Master (150.64 KB, image/png)
2019-01-16 16:31 UTC, Xisco Faulí
Details

Note You need to log in before you can comment on or make changes to this bug.
Description byronigoe 2019-01-14 20:25:58 UTC
Description:
I received an XLSB file and opened it in LibreOffice Calc. The total formulas at the bottom show different numbers than if you open the same file in MS Excel. It seems that some rows were hidden in the Microsoft file, but Calc shows them. This causes the cell references to be out of sync, and thus incorrect.

Steps to Reproduce:
0. Open the attached file in both LibreOffice Calc and Microsoft Excel
1. Look at cell F72 in both
2. Look at cell D18 in both

Actual Results:
1. 131,400
2. TJ681AAE

Expected Results:
1. 107,100
2. TG627BA


Reproducible: Always


User Profile Reset: Yes



Additional Info:
Comment 1 byronigoe 2019-01-14 20:27:34 UTC
Created attachment 148316 [details]
Illustrates the bug
Comment 2 Durgapriyanka 2019-01-15 16:00:21 UTC
Thank you for reporting the bug. I can confirm this bug in

Version: 6.3.0.0.alpha0+
Build ID: 3c964980da07892a02d5ac721d80558c459532d0
CPU threads: 2; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2018-12-12_02:07:45
Locale: en-US (en_US); UI-Language: en-US
Calc: threaded
Comment 3 Xisco Faulí 2019-01-16 16:31:49 UTC
Created attachment 148365 [details]
comparison MSO 2010 and LibreOffice 6.3 Master
Comment 4 Xisco Faulí 2019-01-16 16:34:22 UTC
Also reproduced in

Version: 5.2.0.0.alpha0+
Build ID: 3ca42d8d51174010d5e8a32b96e9b4c0b3730a53
Threads 4; Ver: 4.15; Render: default; 

Version 4.1.0.0.alpha0+ (Build ID: efca6f15609322f62a35619619a6d5fe5c9bd5a)

LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 5 QA Administrators 2021-01-16 04:16:54 UTC Comment hidden (obsolete)
Comment 6 Roman Kuznetsov 2021-01-29 12:31:41 UTC
still repro in

Version: 7.2.0.0.alpha0+ (x64)
Build ID: 94f6765d6ecc3145fa2d266231124003cf953118
CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: Skia/Raster; VCL: win
Locale: ru-RU (ru_RU); UI: en-US
Calc: threaded
Comment 7 QA Administrators 2023-01-30 03:21:51 UTC Comment hidden (obsolete)
Comment 8 ady 2023-05-29 17:31:06 UTC
The Pivot Table is imported differently in Calc than in Excel.

Be careful not to click on row 4, so as not modify the Pivot Table itself.

Examples (cells) to compare between Excel and Calc:

_ F4, Calc does not consider the column as part of the PT.

_ F18 (900 <> 0)
_ B18:C19 (grouped, empty vs another item)

So row 18 complicates the comparison of differences, and generates the offset in the resulting sums.


_ B27:C30 (Excel) vs B29:C32 (Calc) and their respective values in column F.

_ B44:C45 (Excel) vs B48:C49 (Calc) and their respective values in column F.

_ B54:C55 (Excel) vs B58:C59 (Calc) and their respective values in column F.

_ B59 (Excel) vs B63 (Calc).

Obviously that, starting from row 18, each row has different values in column F; some might coincide, but only by chance.


IOW, Calc imports differently column F and row 18 in the Pivot Table, shifting the rest of the content and calculations.
Comment 9 QA Administrators 2025-05-29 03:12:51 UTC
Dear byronigoe,

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