https://bugs.documentfoundation.org/show_bug.cgi?id=168257

            Bug ID: 168257
           Summary: problem with a pivot table in LibreOffice calc version
                    25.8.1 pivot table still displays the labels from the
                    previous data range
           Product: LibreOffice
           Version: 25.8.1.1 release
          Hardware: All
                OS: Windows (All)
            Status: UNCONFIRMED
          Severity: normal
          Priority: medium
         Component: Calc
          Assignee: [email protected]
          Reporter: [email protected]

Description:
I have a problem with a pivot table in LibreOffice calc version 25.8.1. The
issue is that when I select/filter a different data range in the pivot table,
the chart linked to the pivot table still displays the labels from the previous
data range. In other words, the labels at the bottom of the chart don’t update
and remain the old ones.

This issue did not occur in version 25.2; it started after updating to the
current version. That’s why today I downloaded the Portable version 25.2.3.2,
and there, after changing the range in the pivot table, the chart along with
the labels at the bottom updated correctly.

Steps to Reproduce:
1.Create a Pivot Table with some data.

2. Insert a chart based on this Pivot Table.

3. Change the data range in the Pivot Table (e.g. by filtering or selecting a
different field).


Actual Results:
After changing the data range in the Pivot Table, the chart kept showing the
old category labels at the bottom. The labels did not update to reflect the new
Pivot Table data.

Expected Results:
The chart should have updated automatically, including the category labels at
the bottom, to match the new data from the Pivot Table.


Reproducible: Always


User Profile Reset: No

Additional Info:
This bug started in LibreOffice 25.8.1.

It worked correctly in LibreOffice 25.2.3.2 (tested with Portable version).

Operating System: Windows 11 pro 64-bit].

Reproducible: always.

-- 
You are receiving this mail because:
You are the assignee for the bug.

Reply via email to