Bug 89138 - PIVOTTABLE: References to cells of pivottable are not correctly saved; cached results not saved
Summary: PIVOTTABLE: References to cells of pivottable are not correctly saved; cached...
Status: RESOLVED WORKSFORME
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
4.3.5.2 release
Hardware: x86 (IA32) All
: medium normal
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2015-02-05 16:27 UTC by Jürgen Mähnß
Modified: 2016-02-26 15:29 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments
Testfiles as described (66.60 KB, application/x-zip-compressed)
2015-02-05 16:27 UTC, Jürgen Mähnß
Details

Note You need to log in before you can comment on or make changes to this bug.
Description Jürgen Mähnß 2015-02-05 16:27:35 UTC
Created attachment 113147 [details]
Testfiles as described

Situation: Table with scattered values (ref-p1#t1) are analyzed by pivot and saved in an extra table in the same file (ref-p1#t2).
A second file (ref-p2) contains two tables and makes references in table t2 to that pivot table in ref-p1#t2. A third one (ref-p3) references back to the second. 
Effect: Opening ref-p2 shows not the values of the references to the pivot-table in ref-p1#t2 but instead values of the reference to the cells in ref-p1#t1.
Refreshing reveals the current bindings. Storing does not store the correct values which can be seen after reopenng or referencing with a third file (ref-p3).
Testfiles attached: ref-p1, ref-p2, ref-p3
Comment 1 Jürgen Mähnß 2015-02-05 16:39:56 UTC
Same failure detected in LO 4.3.3
Comment 2 Jürgen Mähnß 2015-02-05 18:10:06 UTC
works fine with 4.2.4.2, unsure about 4.3.3
Comment 3 raal 2015-02-06 14:30:29 UTC
Hello,

> 
> Situation: Table with scattered values (ref-p1#t1) are analyzed by pivot and
> saved in an extra table in the same file (ref-p1#t2).
> A second file (ref-p2) contains two tables and makes references in table t2
> to that pivot table in ref-p1#t2. A third one (ref-p3) references back to
> the second. 
> Effect: Opening ref-p2 shows not the values of the references to the
> pivot-table in ref-p1#t2 but instead values of the reference to the cells in
> ref-p1#t1.

I opened file ref-p2 in LO 4.4.0.3 and cell t2.B2 show formula
='file:///C:/temp/pivot-ref/ref-p1.ods'#$t2.B2   and value 10,92
Is it correct?
Comment 4 Jürgen Mähnß 2015-02-06 16:01:55 UTC
Yes, this is correct.
In my systems (both win7prof and win8prof) I experience now the behaviour, that the values are correct when I start LO the first time after system start. When I close the file ref-p2 and reopen it therafter, the values are not correct until I refreh the bindings. Saving doesn't change the effect. When I open ref-p3 I see the wrong values.
Comment 5 Jürgen Mähnß 2015-02-06 16:22:17 UTC
I tested on two different systems (other than mentioned in commet 4: 
win 7-32 professional and win 8.1-64 enterprise both LO 4.4.0.3 and on a win 7-32 professional LO 4.3.5.2. So the spec set about hardware and os might be not set correct by me.

The description in comment 4 was generested with the win 8.1-64 and LO 4.3.5.2.
Comment 6 raal 2015-02-07 07:56:43 UTC
Three files with linear binding
Source File p1 <- P2 <- P3
File P2 is not caching results. When refresh bindings in P2 and P3, then everything works. P2 doesn't cache results after the save.


I can confirm with  4.4.0.3, ID build: de093506bcdc5fafd9023ee680b8c60e3e0645d7, win7

I can confirm with Version: 4.5.0.0.alpha0+
Build ID: 40432ac6caa478474d73786f95b808c14e106ff2
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:master, Time: 2015-02-03_01:24:42
Comment 7 QA Administrators 2016-02-21 08:34:30 UTC
** Please read this message in its entirety before responding **

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 on a currently supported version of LibreOffice 
   (5.0.5 or 5.1.0)  https://www.libreoffice.org/download/

   If the bug is present, please leave a comment that includes the version of LibreOffice and 
   your operating system, and any changes you see in the bug behavior
 
   If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave 
   a short comment that includes your version of LibreOffice and Operating System

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)

http://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: http://webchat.freenode.net/?channels=libreoffice-qa

Thank you for your help!

-- The LibreOffice QA Team This NEW Message was generated on: 2016-02-21
Comment 8 Jürgen Mähnß 2016-02-26 15:16:16 UTC
works fine in Version: 5.1.0.3 (x64)
Build-ID: 5e3e00a007d9b3b6efb6797a8b8e57b51ab1f737
Comment 9 raal 2016-02-26 15:29:54 UTC
correct status