Download it now!
Bug 124766 - Exported pivot table crashes Excel when modifying years filter
Summary: Exported pivot table crashes Excel when modifying years filter
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
(earliest affected)
Hardware: All All
: medium normal
Assignee: Not Assigned
Keywords: filter:xlsx
Depends on:
Blocks: XLSX-Corrupted Pivot-Table-XLSX
  Show dependency treegraph
Reported: 2019-04-16 08:49 UTC by Mike Kaganski
Modified: 2019-08-07 13:27 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:

sc/qa/unit/data/xlsx/pivot-table/shared-dategroup.xlsx (17.13 KB, application/vnd.openxmlformats-officedocument.spreadsheetml.sheet)
2019-04-16 08:49 UTC, Mike Kaganski

Note You need to log in before you can comment on or make changes to this bug.
Description Mike Kaganski 2019-04-16 08:49:22 UTC
Created attachment 150781 [details]

In current master (after

1. Open the attachment (out unit test document) and re-save back to XLSX;
2. Open the result in Excel 2016;
3. Clicking the drop-down button next to "a" in any of the pivot tables;
4. Apply any modification to the list (like unchecking "1965") and confirm OK.
=> Excel crashes (just disappears without error messages; next launch shows recovery panel).

Refreshing pivots in Excel before operation prevents crash.

This is not strictly a regression, since it is likely related to the new functionality (export of group fields) previously missing in LO XLSX export filter.
Comment 1 Roman Kuznetsov 2019-04-16 09:12:50 UTC
confirm for MS Excel 2010 after resave to XLSX in

Build ID: 3083fe569f96bf0289da1e9d0ef7da15ab22e2f6
CPU threads: 4; OS: Windows 6.1; UI render: default; VCL: win; 
TinderBox: Win-x86@42, Branch:master, Time: 2019-04-16_01:39:55
Locale: ru-RU (ru_RU); UI-Language: en-US
Calc: threaded
Comment 2 Xisco Faulí 2019-08-07 13:23:56 UTC
Hi Mike,
Is the the same as bug 126748 ?
Comment 3 Xisco Faulí 2019-08-07 13:24:19 UTC
(In reply to Xisco Faulí from comment #2)
> Hi Mike,
> Is the the same as bug 126748 ?

same root cause*
Comment 4 Mike Kaganski 2019-08-07 13:27:52 UTC
(In reply to Xisco Faulí from comment #3)

No, the root causes are completely different. Yes, they both are related to the same commit.