Export to linked file fails with "Invalid column index 16385" after the file was edited in an office suite

Abierto
#3,831 1 comentario 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
3/5
Tiempo estimado
1-2 días
Aptitud para principiantes
45/100
Tipo de issue
Error
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
php
Área
backend

Línea de trabajo

Start in SubmissionService::exportData, where the existing linked spreadsheet is loaded and its columns and rows are synced, and follow the calls to getHighestColumn() and removeColumnByIndex. SyncSubmissionsWithLinkedFileJob hits the same path in the background. Reproduce by loading a spreadsheet whose row 2 has styled cells out to column XFD and checking which column index is passed in. Done means the export either succeeds on that file or stops with a clear error, and the maintainers still need to pick between those two behaviours.

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

Descripción

0. Needs triage bug

Exporting submissions into an existing (linked) spreadsheet fails once that file has been opened and saved in an office suite (Collabora/Nextcloud Office). The UI shows "Error while exporting to Files" and the log contains:

PhpOffice\PhpSpreadsheet\Exception: Invalid column index 16385
Since 5.4.0 the export loads the existing file and syncs columns/rows into it (SubmissionService::exportData). After saving in an office suite, row-level formatting (e.g. on the hidden ID row 2) makes getHighestColumn() return the last possible column (XFD = 16384). The column sync (removeColumnByIndex / writing the header) then addresses column 16385, which PhpSpreadsheet rejects.

Steps to reproduce
Create a form, add a submission.
Results → "Export to Files" (xlsx), so the form gets a linked file.
Open the exported xlsx in Nextcloud Office (Collabora), change nothing or format a cell, save.
Add another submission, or export to Files again.
Export fails; the background sync (SyncSubmissionsWithLinkedFileJob) fails the same way.
Expected behavior
The export either works on a file edited in an office suite (e.g. by using getHighestDataColumn() instead of getHighestColumn() and ignoring styled-but-empty cells), or fails with a clear message such as "The linked file was changed outside Forms – please unlink or rename it".

Workaround
Rename or move the edited file and unlink it, then export again (a fresh file is created).

Environment
Forms 5.4.0 (code path unchanged in 5.4.1 and main as of 2026-11-03)
Nextcloud 34.0.5, Docker image nextcloud:34.0.5-apache
Office: Collabora Online (richdocuments 11.1.2)

Lenguaje dominante
JavaScript
Estrellas
385
Forks
133
Merge medio
7 h 54 min
PR fusionados (30 d)
157

Preparar el entorno

Abrir en Codespaces

Inicia el contenedor de desarrollo del proyecto en tu navegador, con tu propia cuenta de GitHub.

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 nextcloud/forms

Todos los issues de nextcloud/forms

Issues similares

Más issues de JavaScript

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.