In excel, to reference the data in a pivot table for a chart you select one cell of the pivot table.
In OnlyOffice you have to select the whole data range which breaks the chart if entries are added to or removed from the pivot table.
Is there a way to reference the whole pivot table dynamically in charts?
Hello @Heinz
To be honest, I’m not sure that I understood the request right. I had an old file with pivot table on hand on which I checked the work with charts. The chart works regardless of whether I select the entire range or just a few values. Could you please clarify the issue scenario along with a test file and record of your actions?
here’re my actions and test file:
test.xlsx (21.9 KB)
In your example, the pivot table doesn’t actually gain an entry, it’s just the filters that change.
I can’t attach something here so here is a YouTube link to a video.
In this video I first create a pivot table from a range of data plus some blank space to add entries later. I then edit the pivot table to only show what’s interesting me and proceed to make a chart.
Here I set the data range to the pivot table, at this point, everything works as expected.
When adding a new category to the data range and refreshing the pivot table, it also gets the new category added which isn’t reflected in the chart as the data range doesn’t adjust to the new range of the pivot table.
One solution I thought of was to extend the data range of the chart below the actual pivot table as I did before when creating the pivot table but as seen in the video when I remove the entry again, if there is empty space below the pivot table referenced in the chart it leaves an entry in the charts legend which gets messy with more empty space.
What I would need is a way to reference the pivot table that adjusts automatically so that new entries are reflected in the chart and removed ones disappear.
Thank you for the video and detailed description! We are checking the situation, I will contact you as soon as possible.
Hello @Heinz
I want to thank you for the provided file and detailed description once again!
We have reviewed the situation and found a bug. We have started working on it. I will update this thread once we have something to share.