https://bugs.documentfoundation.org/show_bug.cgi?id=162968
--- Comment #18 from Eyal Rozenberg <[email protected]> --- (In reply to Tomaz Vajngerl from comment #17) > (In reply to Eyal Rozenberg from comment #16) > > We just agreed that PivotCharts, even now, do not reflect the data in a > > single way. XY-scatter charts reflect it one way, Column charts reflect it > > another way. Thus, creating by-row rather than by-column data series charts > > is not a deviation from "the" way; it's just yet another way. > > No, that's the representation of the data that is different. "Reflection", "representation" - you're splitting hairs. Transposition is literally a reflection. > It reflects the > data in a way that row fields are (main) axis data and column fields are > each its own data series. That stays the same independent on the type of the > chart. That's the bug. There is no reason to force this being the case. A table can be read as columns or as rows - whether it's a PivotTable or not. > OOXML interoperability issue between LO and MSO (and other editors that can > read OOXML and support PivotCharts). To reflect the data in a different way > would need a LO specific extension to the standard (or a solution to put the > PivotTable internal to the PivotChart - which brings this back to the first > possible solution I described). The fact that MSO or OOXML don't support something, and we add support for it - is not an interoperability issue. If we spreadsheets with the feature set common between both apps, or LO and OOXML, were to have problems going in one direction or the other - that would be an interop issue. But indeed, if OOXML cannot represent this, such a PivotChart could not be saved to an OOXML (without an LO extension). And now that you raise this question - I suppose we also have to ask whether ODTs will have a problem with this. -- You are receiving this mail because: You are the assignee for the bug.
