XLSX export: optional native Excel PivotTable

Ouverte
#372 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 1 jour

Personne n'a encore pris cette issue.

Évaluation

Difficulté
5/5
Temps estimé
Plus d'une semaine
Accessibilité débutants
20/100
Type d'issue
Fonctionnalité
Clarté
À clarifier
Activité
Active
Stack technique
javascript, openapi, react

Piste de recherche

Read the XLSX writer and the export paths for the UI, CLI, REST, and MCP render_view mentioned in the issue, then inspect how exportData and the REST/MCP exposure policies are enforced. The issue leaves the design, size limits, and OOXML implementation open; first define those decisions and test how generated files open in Excel, LibreOffice, and Numbers without repair prompts. Done means an optional PivotTable export respects exposure controls and faithfully represents unsupported view features.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

area:core area:report enhancement idea

Today the XLSX export writes the pivot result as a plain table. Some people want to keep working in Excel: open the file and change rows, columns and filters there. For that the workbook needs a real Excel PivotTable.

Idea: an optional export "Workbook with Excel PivotTable" (UI, CLI --format xlsx --pivot-table, REST/MCP render_view):

  • a data sheet with the rows the view needs, a pivot cache over it (pivotCacheDefinition, pivotCacheRecords) and a pivot table (pivotTable) laid out like the view: rows, columns, values with their aggregation, filters as page fields or item selections;
  • what has no Excel equivalent (derived fields such as "Date by month", show-as, value filters on totals, relative dates) is either written as a helper column or listed in a note sheet, never silently dropped;
  • the chart (#360) could become a PivotChart on the same cache.

Open points:

  • The file then contains the source rows, not only the result. That must follow exportData in the UI and the exposure policy (summary/hide, results) in REST and MCP, and is off by default.
  • The XLSX writer is hand-written (no SheetJS, no ExcelJS); the pivot parts are a larger piece of OOXML to write and test, including Excel, LibreOffice and Numbers opening it without a repair prompt.
  • Size limits for the data sheet.

Related: #360, #364.

Langage dominant
JavaScript
Étoiles
1
Forks
1
Merge moyen
3 h 34 min
PR mergées (30 j)
213

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de eizedev/pivotkit

Toutes les issues de eizedev/pivotkit

Issues similaires

Plus d'issues JavaScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.