Bug 122897 - FILESAVE XLSX Spreadsheet with Database Range is incorrect when the document is opened in Excel
Summary: FILESAVE XLSX Spreadsheet with Database Range is incorrect when the document ...
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
5.2 all versions
Hardware: All All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: bibisected, bisected, filter:xlsx, regression
Depends on:
Blocks: XLSX-Corrupted Calc-DataRange
  Show dependency treegraph
 
Reported: 2019-01-23 12:09 UTC by NISZ LibreOffice Team
Modified: 2020-10-17 11:57 UTC (History)
6 users (show)

See Also:
Crash report or crash signature:


Attachments
Screenshot of the problem in Excel. (120.85 KB, image/png)
2019-01-23 12:12 UTC, NISZ LibreOffice Team
Details
Example file from Calc with database range. (12.44 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2019-01-23 12:13 UTC, NISZ LibreOffice Team
Details
Bibisect log file (2.41 KB, text/plain)
2019-01-28 11:59 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 2019-01-23 12:09:17 UTC
Description:
Spreadsheet with Database Range is incorrect when the document is opened in Microsoft Excel.

Steps to Reproduce:
    1. Create a new spreadsheet in LibreOffice Calc.
    2. Create a Database Range. (Data→Define Database Range)
    3. Save the file as XLSX.
    4. Open the same file in Microsoft Excel.

Actual Results:
Error message: Excel found unreadable content in filename...
Excel was able to open the file by repairing or removing the unreadable content.

Expected Results:
Spreadsheet should open correctly in Excel. The first row of the database range shouldn’t be header row.



Reproducible: Always


User Profile Reset: No



Additional Info:
Comment 1 NISZ LibreOffice Team 2019-01-23 12:12:23 UTC
Created attachment 148551 [details]
Screenshot of the problem in Excel.
Comment 2 NISZ LibreOffice Team 2019-01-23 12:13:11 UTC
Created attachment 148552 [details]
Example file from Calc with database range.
Comment 3 Durgapriyanka 2019-01-23 17:19:24 UTC
Thank you for reporting the bug. I can confirm this 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 4 Xisco Faulí 2019-01-24 10:25:10 UTC
Also reproduced in

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

but not in

Version: 4.3.0.0.alpha1+
Build ID: c15927f20d4727c3b8de68497b6949e72f9e6e9e
Comment 5 Buovjaga 2019-01-26 20:45:59 UTC
NISZ Team: would it be possible for you to bibisect this as having MSO + bibisecting capabilities is a somewhat rare combination? You can follow this tutorial, if there is need for training: https://wiki.documentfoundation.org/QA/Bibisect/Bibisecting_tutorial
Comment 6 NISZ LibreOffice Team 2019-01-28 11:59:01 UTC
Created attachment 148708 [details]
Bibisect log file

Bibisected with: bibisect-win32-5.1

Regression introduced by:
commit 61d203fab63ef4f4863e8b2308e62bd245aa62db [log] 
author Eike Rathke <erack@redhat.com> Mon Aug 31 20:55:18 2015 +0200 
committer Eike Rathke <erack@redhat.com> Mon Aug 31 20:56:12 2015 +0200 
tree 265ab6dc301f451ef57dce8f467110a2c310eb57 
parent f284678e334b02808a6c2d473ce683745c99d08e [diff]


But:
In the previous versions the Database Range is lost, when the spreadsheet is saved in XLSX format.
Comment 7 Buovjaga 2019-01-28 12:19:21 UTC
(In reply to NISZ LibreOffice Team from comment #6)
> But:
> In the previous versions the Database Range is lost, when the spreadsheet is
> saved in XLSX format.

Ok, so it's not a regression after all, but an improvement.
Comment 8 raal 2019-01-28 13:43:20 UTC
This seems to have begun at the below commit.
Adding Cc: to Eike Rathke; Could you possibly take a look at this one? Thanks

f0f65f2aeef6afe9b25d9d7c97afc4f59539b6fe is the first bad commit
commit f0f65f2aeef6afe9b25d9d7c97afc4f59539b6fe
Author: Norbert Thiebaud <nthiebaud@gmail.com>
Date:   Tue Sep 1 16:44:44 2015 -0700

    source sha:61d203fab63ef4f4863e8b2308e62bd245aa62db

    source sha:61d203fab63ef4f4863e8b2308e62bd245aa62db
    source sha:f284678e334b02808a6c2d473ce683745c99d08e
    source sha:8709571dc5a595fbc51b25e159fbd944fcb2ebc1
    source sha:ef89f94b26e61b43451f1f4f685a55aaa959311c

author    Eike Rathke <erack@redhat.com>    2015-08-31 20:55:18 +0200
committer    Eike Rathke <erack@redhat.com>    2015-08-31 20:56:12 +0200
commit    61d203fab63ef4f4863e8b2308e62bd245aa62db (patch)
tree    265ab6dc301f451ef57dce8f467110a2c310eb57
parent    f284678e334b02808a6c2d473ce683745c99d08e (diff)
TableRef: adapt to ::std::vector<std::unique_ptr<ScDBData>> change
Change-Id: I8f84bb5f4a988b5fb2b688e3c5be321c39818259

author    Eike Rathke <erack@redhat.com>    2015-08-31 19:52:27 +0200
committer    Eike Rathke <erack@redhat.com>    2015-08-31 19:59:38 +0200
commit    f284678e334b02808a6c2d473ce683745c99d08e (patch)
tree    0b83aa57871e3c57de2ca8fd60864b3101f5a10a
parent    8709571dc5a595fbc51b25e159fbd944fcb2ebc1 (diff)
TableRef: write OOXML table autoFilter fragment

author    Eike Rathke <erack@redhat.com>    2015-08-31 18:48:46 +0200
committer    Eike Rathke <erack@redhat.com>    2015-08-31 19:59:38 +0200
commit    8709571dc5a595fbc51b25e159fbd944fcb2ebc1 (patch)
tree    08d3b64931616c6842663743ef74a9edc6bf008e
parent    ef89f94b26e61b43451f1f4f685a55aaa959311c (diff)
TableRef: write OOXML tableColumns,tableColumn

author    Eike Rathke <erack@redhat.com>    2015-08-31 15:53:33 +0200
committer    Eike Rathke <erack@redhat.com>    2015-08-31 19:59:37 +0200
commit    ef89f94b26e61b43451f1f4f685a55aaa959311c (patch)
tree    f8d705faf97cca6cf66244514a7830b153350e3e
parent    3dabb0692d496684ba145cc95884a731ca1cd5b0 (diff)
TableRef: first wave of writing ScDBData to OOXML tables