Bug 129795 - PIVOTTABLE - Can't change pivot table destination (overlapping destination)
Summary: PIVOTTABLE - Can't change pivot table destination (overlapping destination)
Status: NEW
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: Calc (show other bugs)
Version:
(earliest affected)
6.3.3.2 release
Hardware: x86-64 (AMD64) Windows (All)
: medium minor
Assignee: Not Assigned
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: Pivot-Table
  Show dependency treegraph
 
Reported: 2020-01-04 21:53 UTC by jwmp5051@gmail.com
Modified: 2024-04-11 03:13 UTC (History)
2 users (show)

See Also:
Crash report or crash signature:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description jwmp5051@gmail.com 2020-01-04 21:53:26 UTC
Description:
Related to Bug 89308 - PIVOTTABLE: Can't update pivot table destination

Using LibreOffice Calc Version@ 6.3.3.2 (x64)
OS: Windows 10

This issue does not move the pivot table if it overlaps the previous copy (i.e. cannot create a copy on top of the existing table). Nor can you move it by inserting columns or rows beside or above the table.
If you do move the pivot table to a non-overlapping region, then the associated graph is deleted.



Steps to Reproduce:
Create a pivot table and associated graph of the data.

1. Attempt to move the pivot table by inserting a column to the left (or row above). Pivot table moves correctly on the spreadsheet (but destination is not updated in the properties).
2. Refresh the table. Pivot table reverts to the original location.
3. Use Properties -> Source and Destination -> Selection to manually alter the column (or row) by one letter. Click OK. Pivot Table does not move, Destination remains the same.
4. Try the same by selecting the desired location with the mouse. Pivot Table does not move.
5. Change the destination to a non-overlapping location. The associated graph is deleted (following a confirmation prompt).



Actual Results:
Pivot table does not move

Expected Results:
Table reverts / remains in original location


Reproducible: Always


User Profile Reset: No


OpenGL enabled: Yes

Additional Info:
I understand that moving the table is currently a copy/delete procedure and may not be easily fixed. I just wanted to highlight the issue in case someone had a bright idea.
Comment 1 m_a_riosv 2020-01-04 22:51:29 UTC
Repro
Versión: 6.3.4.2 (x64)
Id. de compilación: 60da17e045e08f1793c57c00ba83cdfce946d0aa
Subprocs. CPU: 4; SO: Windows 10.0; Repres. IU: GL; VCL: win; 
Configuración regional: es-ES (es_ES); Idioma de IU: es-ES
Calc: CL
Comment 2 QA Administrators 2022-04-11 03:31:20 UTC Comment hidden (obsolete)
Comment 3 jwmp5051@gmail.com 2022-04-11 22:59:20 UTC
Tested on 2022-11-04 with:
Version:        7.3.2.2 (x64)
Build:          49f2b1bff42cfccbd8f788c8dc32c1c309559be0
Environment:    CPU Threads: 8; OS: Windows 10.0 Build 19043
User Interface: UI render: Skia/Vulkan; VCL: win
Locale:         en-GB (en-GB); UI: en-GB
Misc:           Calc: CL

1. Attempt to move the pivot table by inserting a column to the left (or row above). Pivot table moves correctly on the spreadsheet (but destination is not updated in the properties).

FIXED - This now works correctly. The associated graph data range does follow the pivot table movement.

2. Refresh the table. Pivot table reverts to the original location.

FIXED - This no longer happens.

3. Use Properties -> Source and Destination -> Selection to manually alter the column (or row) by one letter. Click OK. Pivot Table does not move, Destination remains the same.

NOT FIXED - If the destination point lies within the current pivot table, then the table does not move and the destination does not change.
If the destination point lies outside the current table, but the resulting moved table would overlap the current table, then a pop-up is displayed: "The destination range is not empty. Overwrite existing contents?" If Yes is clicked, then sometimes the table is deleted, sometimes there appears to be a duplicate over the original.
If the destination is outside the current pivot table and the moved table would not overlap the existing, then the move is performed correctly.
In any of the above situations, the graph data does not update to follow the moved table - presumably because the table is a copy of the original.

4. Try the same by selecting the desired location with the mouse. Pivot Table does not move.

NOT FIXED - As 3.

5. Change the destination to a non-overlapping location. The associated graph is deleted (following a confirmation prompt).

FIXED - The graph is no longer deleted, though the data range does not follow the move.

COMMENT:
Obviously this is a rare edge case since nobody else seems to be reporting the same experiences here. As for me, I only brought it to your attention because of the unusual behaviour. It does not affect me otherwise since there are workarounds (and I don't need to do this often, if at all).

Best regards,
John
Comment 4 jwmp5051@gmail.com 2022-04-11 23:04:10 UTC
I forgot to mention with regards to problem 3:

Using Ctrl + z to undo changes after a move often results in some very odd graphical anomalies! It becomes so messy that it is safest to reload from disk.
Comment 5 QA Administrators 2024-04-11 03:13:25 UTC
Dear jwmp5051@gmail.com,

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