XLSX export: optional native Excel PivotTable

Abierto
#372 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
20/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Activo
Stack tecnológico
javascript, openapi, react

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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.

Lenguaje dominante
JavaScript
Estrellas
1
Forks
1
Merge medio
3 h 34 min
PR fusionados (30 d)
213

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de eizedev/pivotkit

Todos los issues de eizedev/pivotkit

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.