https://bugs.documentfoundation.org/show_bug.cgi?id=158054
--- Comment #6 from Stéphane Guillou (stragu) <[email protected]> --- Created attachment 190984 --> https://bugs.documentfoundation.org/attachment.cgi?id=190984&action=edit smaller sample ODS for comment 6 steps (In reply to Luca A. from comment #5) > first of all, thank you for your kind attention! Thank you for reporting issues! > I turned back my LibrOffice version from 7.6 back to 7.5. > Then I erased and rebuilt the single pivot tables, that were not working > everytime I tried to update them. > [...] > The good news is that now these recent new tables work correctly as usual, > so I cannot reproduce the issue. Glad you have a working version. Which 7.5 release is it exactly? In any case, this might mean that we have a regression in 7.6, which is important to identify if we can. I know of one sheet reference-related regression in 7.6: bug 158223. The thing I could reproduce: 1. Open this attachment (based on yours) 2. Check that Pivot table in Ago23 does work 3. Delete Sheet3. Result A: Even though buttons are still there, the pivot table is inactive, can't be refreshed or interacted with. 4. Save and reload. Result B: the area is recognised as a pivot table (can use e.g. Edit or Refresh), but it has no effect. 5. Right-click > Refresh the pivot table; 6. Save and reload. Result C: no more buttons; area is still recognised as a pivot table, still inactive. Let's focus on this aspect of the issue, as we have reproduction steps (even though we don't have steps for the overlap of tables). Reproduced in: Version: 7.6.3.1 (X86_64) / LibreOffice Community Build ID: c4af5b1259bceea6e979e6fe2435dbee7a5a87c2 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded Not reproduced with: Version: 7.5.8.2 (X86_64) / LibreOffice Community Build ID: f718d63693263970429a68f568db6046aaa9df01 CPU threads: 8; OS: Linux 5.15; UI render: default; VCL: gtk3 Locale: en-AU (en_AU.UTF-8); UI: en-US Calc: threaded -- You are receiving this mail because: You are the assignee for the bug.
