What a Pivot Table Becomes When You Download It as an .xlsx File
Piskes Sheets drops pivot tables and charts on .xlsx export with a named warning, rather than trying to fake a format it can't cleanly represent — and telling you it happened matters more than the drop itself.
"Does this export cleanly to Excel" is a question worth asking before you hand a colleague a file you built somewhere else, and the honest answer for Piskes Sheets isn't a blanket yes. Pivot tables — like charts — are dropped when you export a Piskes Sheets file as .xlsx, and the export process raises a named warning telling you it happened, rather than silently producing a file that looks complete but is quietly missing the thing you actually cared about.
Why the drop happens at all
A pivot table in Piskes Sheets, as covered elsewhere, is a live spec — a row field, a column field, an aggregation — evaluated against the current workbook, not a static block of pre-computed cells. Excel's own pivot table format is a different, more complex structure with its own internal representation that isn't a direct match for what Piskes Sheets is actually storing. Faithfully round-tripping a live, dynamically computed pivot into Excel's native pivot format isn't a small mapping problem, and rather than ship something that half-works — an .xlsx file with a pivot table that looks right until you try to refresh it, or breaks in some Excel version but not another — the export path drops it and says so.
Why "silently" would be the actual failure
The distinction that matters here isn't that a limitation exists — every export path between formats has some. It's that the alternative to a named warning is silence: a colleague opens the .xlsx file expecting a pivot table, doesn't find one, and has no way to know whether it was dropped on export, never existed, or got deleted somewhere along the way. A named warning at export time turns an invisible gap into a visible, explainable one — you know before you send the file, not after someone else opens it and asks you where the pivot went.
What this means practically
If a file you're exporting to hand off to someone on Excel includes a pivot table, that pivot won't make the trip — expect the underlying data to carry over, but plan to note separately (or rebuild) whatever the pivot was summarizing on the Excel side, since it won't be waiting there for you. Worth checking directly against the export path (frontend/apps/drive/src/lib/office/univer-xlsx.ts) if you need the exact wording of the warning for your own documentation or a support conversation, since this is a specific, checkable behavior rather than a general statement about export limitations.