https://bz.apache.org/bugzilla/show_bug.cgi?id=63463
--- Comment #1 from Chris Dufour <chris.duf...@mindbridge.ai> ---
We also ran into this issue when upgrading from 3.1.5 4.1.0.
It appears the cause is the sheet.shiftRows function.
Our code shifted some rows up one column after removing some templating fields.
There is a snippet I extracted from within an (unzipped) XLSX sheet:
myDoc/xl/worksheets/sheet1.xml
<row r="11" spans="1:27" ht="19">
<c r="A12" s="15" t="s">
<v>67</v>
</c>
<c r="B12" s="16" t="s">
<v>68</v>
</c>
<c r="C12" s="15" t="s">
<v>69</v>
</c>
...
</row>
It appears that the shift function is correctly updating the row property of
the rows (r="11") but not the row/column value for the cell (r="A12"). This
results in the XLSX file being in an invalid state, which Microsoft Excel, and
likely other Spreadsheet programs, treat as corrupted.
All both of 4.1.0 and 4.0.1 appear to have this issue, meaning that it was
probably caused by some change in the 4.0.0 release.
We are using XSSFWorkbook (workbook.getSheetAt(sheet).shiftRows(x, y, -1)), but
this may also affect other workbook formats.
--
You are receiving this mail because:
You are the assignee for the bug.
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@poi.apache.org
For additional commands, e-mail: dev-h...@poi.apache.org
