Bug 60169 - PIVOTTABLE Custom grand total name is not persistent when saved in xls
Summary: PIVOTTABLE Custom grand total name is not persistent when saved in xls
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: Other All
: medium normal
Assignee: Not Assigned
URL: https://bugzilla.novell.com/show_bug....
Whiteboard: interoperability
Keywords: filter:xls
Depends on:
Blocks: Pivot-Table-XLS
  Show dependency treegraph
 
Reported: 2013-02-01 19:24 UTC by Kohei Yoshida
Modified: 2025-12-29 03:21 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Attachments
test doc (10.78 KB, application/vnd.oasis.opendocument.spreadsheet)
2013-02-01 19:24 UTC, Kohei Yoshida
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Kohei Yoshida 2013-02-01 19:24:30 UTC
Created attachment 74064 [details]
test doc

1. Assign a custom name to the grand total name ('Total Result' by default).
2. Save the file as xls.
3. Open it in Excel.
4. Refresh the pivot table.
5. The custom grand total name gets reset to Excel's default name 'Grand
Total'.

OTOH, custom field name and field members names survive the refresh.  It's only
the grand total name that doesn't.  I haven't tested the subtotal names yet.

To reproduce this more easily, open the attached ods document and save it as Excel 97/XP/2003.  Open that saved file in Excel and refresh the pivot table.  The custom grand total name disappears and gets reset to 'Grand Total' (Excel's default).
Comment 1 Kohei Yoshida 2013-02-01 19:25:42 UTC
Still relevant.  Originally filed in bnc.
Comment 2 QA Administrators 2015-04-19 03:22:23 UTC Comment hidden (obsolete)
Comment 3 Buovjaga 2015-06-22 14:25:04 UTC
(In reply to Kohei Yoshida from comment #0)
> 5. The custom grand total name gets reset to Excel's default name 'Grand
> Total'.

Still confirmed.

Win 8.1 32-bit
MSO 2013

LibO Version: 5.1.0.0.alpha1+
Build ID: 2885e157674dbefa7d9b984a399fabd1238eeedd
TinderBox: Win-x86@39, Branch:master, Time: 2015-06-22_07:52:27
Locale: fi-FI (fi_FI)
Comment 4 QA Administrators 2016-09-20 10:10:33 UTC Comment hidden (obsolete)
Comment 5 eisa01 2018-06-16 18:02:29 UTC
Still present, also in LO 3.3 so inherited

Version: 6.2.0.0.alpha0+
Build ID: b292a27698e85fd9d60c03613c3b0c67835c4dc1
CPU threads: 2; OS: Mac OS X 10.12.6; UI render: default; 
TinderBox: MacOSX-x86_64@49-TDF, Branch:master, Time: 2018-06-06_23:25:55
Locale: en-US (en_US.UTF-8); Calc: group threaded
Comment 6 QA Administrators 2021-04-18 03:48:42 UTC Comment hidden (obsolete, spam)
Comment 7 QA Administrators 2023-04-19 03:24:13 UTC Comment hidden (obsolete)
Comment 8 eisa01 2023-12-29 12:35:50 UTC
Still present

Discovered bug 158921 for xlsx

Version: 24.2.0.0.beta1 (AARCH64) / LibreOffice Community
Build ID: 5f390384195b7264c6e52add9e90a39790285249
CPU threads: 10; OS: macOS 14.2; UI render: Skia/Metal; VCL: osx
Locale: en-US (en_US.UTF-8); UI: en-US
Calc: threaded
Comment 9 QA Administrators 2025-12-29 03:21:13 UTC
Dear Kohei Yoshida,

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