Bug 107617 - FILEOPEN PPTX Chart linked to embedded XLSX spreadsheet shows incorrect values
Summary: FILEOPEN PPTX Chart linked to embedded XLSX spreadsheet shows incorrect values
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Chart (show other bugs)
Version:
(earliest affected)
Inherited From OOo
Hardware: All Linux (All)
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords: filter:pptx
Depends on:
Blocks: OOXML-Chart PPTX
  Show dependency treegraph
 
Reported: 2017-05-04 09:29 UTC by antonin.perrotaudet
Modified: 2024-07-21 03:14 UTC (History)
4 users (show)

See Also:
Crash report or crash signature:


Attachments
pptx with graph and linked embeded xlsx (51.06 KB, application/vnd.openxmlformats-officedocument.presentationml.presentation)
2017-05-04 09:29 UTC, antonin.perrotaudet
Details

Note You need to log in before you can comment on or make changes to this bug.
Description antonin.perrotaudet 2017-05-04 09:29:11 UTC
Created attachment 133060 [details]
pptx with graph and linked embeded xlsx

It is not possible to edit an embedded spreadsheet linked by a graph when using the data table widget because the data displayed by this widget is not the data from the embedded spreadsheet.


When embedding a spreadheet in a power point document, and using it in a graph (using data reference, ie <c:externalData r:id="rId101"> if rId101 points to a valid embedded xlsx document), the data displayed in the "data_table" is not the data from the spreadsheet, but the data from graph "<c:numCache>" and "<c:strCache>" elements.

I joined a document as an example : the embedded spreadsheet has for value "Category 1 / Series 1" -> 10 and NOT 4.3


Tested on power point 2010 : power point does read the embedded xlsx document when editing graph data, and updates the graph accordingly.
Comment 1 Buovjaga 2017-05-07 12:01:32 UTC
Confirmed.

Arch Linux 64-bit, KDE Plasma 5
Version: 5.4.0.0.alpha1+
Build ID: 6e4cba99bb35e6697b94309eedd1a08ebea2dc68
CPU threads: 8; OS: Linux 4.10; UI render: default; VCL: kde4; 
Locale: fi-FI (fi_FI.UTF-8); Calc: group
Built on May 5th 2016

Arch Linux 64-bit
LibreOffice 3.3.0 
OOO330m19 (Build:6)
tag libreoffice-3.3.0.4
Comment 2 QA Administrators 2018-10-22 02:49:50 UTC Comment hidden (obsolete)
Comment 3 Babak Razmjoo 2019-03-27 13:39:00 UTC
I may be wrong, but LibreOffice is not supposed to perfectly be able edit MS office files. You can Use Open Document Formats instead. This is the whole point of LibreOffice being free software
Comment 4 Buovjaga 2019-03-27 17:49:53 UTC
(In reply to Babak Razmjoo from comment #3)
> I may be wrong, but LibreOffice is not supposed to perfectly be able edit MS
> office files. You can Use Open Document Formats instead. This is the whole
> point of LibreOffice being free software

We certainly do our best, so you are wrong :)

I still confirm the problem. Category 1 / Series 1 is 10 in the xlsx, but 4.3 in the chart.

Arch Linux 64-bit
Version: 6.3.0.0.alpha0+
Build ID: 66b21521a95f7b2053aa99a23e0a4c34438af6c7
CPU threads: 8; OS: Linux 5.0; UI render: default; VCL: gtk3; 
Locale: fi-FI (fi_FI.UTF-8); UI-Language: en-US
Calc: threaded
Built on 22 March 2019
Comment 5 Balázs Varga 2020-07-17 08:50:58 UTC
I do not understand, what we should achieve here. The value of the first data point is 4.3, in the chart2.xml of the attached file, so we displayed it with the appropriate value.
Also the MS-Office displayed the chart with the correct 4.3 value. Otherwise we do not overwrite the embedded XLSX, we just put it into a grabbag and write out, unchanged. But I think it's unnecessary.
Comment 6 Buovjaga 2020-07-20 11:51:38 UTC Comment hidden (obsolete)
Comment 7 NISZ LibreOffice Team 2020-07-20 12:06:42 UTC
(In reply to Balázs Varga from comment #5)
> Otherwise
> we do not overwrite the embedded XLSX, we just put it into a grabbag and
> write out, unchanged. 

This is the problem here.
PP (and Word) puts an embedded xlsx into the document which we do not change, even if the user changes the data table of the chart.

Such changes are saved to chartN.xml, but not to the grabbagged xlsx.

Once the user opens the LO-saved file in PP/Word and tries to edit its data, they get the grabbagged pre-LO data and at this point any changes made in LO are lost because MSO actualizes the data in chartN.xml from the embedded xlsx.

I'd not say this is NAB, rather that this is a quite difficult bug.
Comment 8 Buovjaga 2020-07-20 12:16:52 UTC Comment hidden (obsolete)
Comment 9 QA Administrators 2022-07-21 03:33:39 UTC Comment hidden (obsolete)
Comment 10 QA Administrators 2024-07-21 03:14:16 UTC
Dear antonin.perrotaudet,

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