Workbook saved using POI 3.16 needs to be repaired when opening in Excel 2016

[Quinton McCombs]

I have run into a problem after upgrading from POI 3.14 to POI 3.16. With
POI 3.14, I can load a workbook, save it, and then open in Excel 2016
without a problem. However, after upgrading to POI 3.16, the workbook needs
to be repaired after opening in Excel. The repaired version of the workbook
loses some formatting and all named ranges are gone.

I have created a test project which loads a workbook and then saves it. The
workbook output.xlsx is corrupted after running the test.



Any help that can be offered would be greatly appreciated!

https://github.com/quintonm/poi-test

[Nick Burch]

Post by Quinton McCombs
I have run into a problem after upgrading from POI 3.14 to POI 3.16.
With POI 3.14, I can load a workbook, save it, and then open in Excel
2016 without a problem. However, after upgrading to POI 3.16, the
workbook needs to be repaired after opening in Excel. The repaired
version of the workbook loses some formatting and all named ranges are
gone.

Can you try a recent nightly build, and see if we've already fixed it
since 3.16?

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@poi.apache.org
For additional commands, e-mail: user-***@poi.apache.org

[pj.fanning]

Could you try poi 3.17?



--
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-User-f2280730.html

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@poi.apache.org
For additional commands, e-mail: user-***@poi.apache.org

[Quinton McCombs]

The same problem occurs with 3.17 as well.

Could you try poi 3.17?>
-->
Sent from: http://apache-poi.1045710.n5.nabble.com/POI-User-f2280730.html>
--------------------------------------------------------------------->

[Quinton McCombs]

The nightly build does not have this problem although 3.17 does. Is there a workaround until 4.0 is released?

On Fri, 22 Jun 2018, Quinton McCombs wrote:>

I have run into a problem after upgrading from POI 3.14 to POI 3.16. >
With POI 3.14, I can load a workbook, save it, and then open in Excel >
2016 without a problem. However, after upgrading to POI 3.16, the >
workbook needs to be repaired after opening in Excel. The repaired >
version of the workbook loses some formatting and all named ranges are >
gone.>

Can you try a recent nightly build, and see if we've already fixed it >
since 3.16?>
Nick>
--------------------------------------------------------------------->

_________________________________________
Quinton McCombs
Guidewire Software | Software Architect
Tel: [phone] x 386 | Cell: [phone]
***@guidewire.com<mailto:***@guidewire.com> | www.guidewire.com<http://www.guidewire.com/>
Adapt and succeed with software products from Guidewire.

[Nick Burch]

Post by Quinton McCombs
The nightly build does not have this problem although 3.17 does. Is
there a workaround until 4.0 is released?

Keep using the nightly build?

(I'd actually recommend a nightly build from about a week ago, there's a
bunch of changes happening right now with xmlbeans in preparation for 4.0
so something just before that may be more stable, though anything that
passes all the unit tests *ought* to be just fine!)

Nick

---------------------------------------------------------------------
To unsubscribe, e-mail: user-***@poi.apache.org
For additional commands, e-mail: user-***@poi.apache.org

[Javen O'Neal]

Since this is an open source project, you could also find the commits in
the svn/git repo that fixed the issue and merge those back into whatever
version of POI you're using.

Generally the POI devs only release hotfixes for security issues, not bugs.

Post by Nick Burch

Post by Quinton McCombs
The nightly build does not have this problem although 3.17 does. Is
there a workaround until 4.0 is released?

Keep using the nightly build?
(I'd actually recommend a nightly build from about a week ago, there's a
bunch of changes happening right now with xmlbeans in preparation for 4.0
so something just before that may be more stable, though anything that
passes all the unit tests *ought* to be just fine!)
Nick
---------------------------------------------------------------------

[Andreas Beeker]

I think this was fixed via #61798 [1], because fixing the dimension in sheet.xml helps.
I haven't tested if this also occurs with other files / use cases, but it's kinda disappointing/interesting
that such a basic operation failure hasn't been noticed earlier.

Andi

[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=61798

[Quinton McCombs]

Thank you for pointing me to the bug for this issue. That will make it much
easier for me to patch 3,17 with only that change.

Post by Andreas Beeker
I think this was fixed via #61798 [1], because fixing the dimension in sheet.xml helps.
I haven't tested if this also occurs with other files / use cases, but
it's kinda disappointing/interesting
that such a basic operation failure hasn't been noticed earlier.
Andi
[1] https://bz.apache.org/bugzilla/show_bug.cgi?id=61798