https://bugs.documentfoundation.org/show_bug.cgi?id=129795
--- Comment #3 from jwmp5...@gmail.com ---
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
--
You are receiving this mail because:
You are the assignee for the bug.
