Created attachment 107662 [details]
House heater dimensioning.
Excel 2013 / Office 365 can´t open a file saved as .xlsx
As attachment here follows a quite large spreadsheet Bergheat46.ods
I can confirm with Version: 18.104.22.168.0+
Build ID: 14907346d792f2f93a00083bbab5086cf56ddb24
TinderBox: Linux-rpm_deb-x86_64@46-TDF, Branch:libreoffice-4-3, Time: 2014-09-26_03:56:08
Excel viewer doesn't open file. I can open file in LO.
@Paavo:could you try to find problematic part of file?
@Paavo:could you try to find problematic part of file?
We can try to find something, but it is not easy to me to find the reason of problem. I hope you can find the reason.
There is also one other minor bug.
In graphics on the first sheet there is text "sub-title".
I can delete this text and save worksheet and all is ok.
A little later, when i am opening it again, this "sub-title" is there again back! Why!
May be this is easier to solve.!
the sheets are protected with password, please upload file without password.
Created attachment 107695 [details]
This the same file without psw.
Created attachment 107696 [details]
Here same file in .xlsx format without psw
@ Paavo: Tools -> protect document -> document
Pass is still here. I want to try delete parts of document to find where is the problem and I'm unable to delete sheet when document is locked.
Created attachment 107698 [details]
Created attachment 107717 [details]
printscreen of workbook.xml
I tried to delete all three sheets and save as xlsx. This file I can not open in excel viewer. So it looks like this file is somewhat broken. New file saved as xlsx I can open in excel viewer without problem.
Please could you verify this? Delete all sheets, save, open in Excel 2013 / Office 365.
I looked into xlsx file, in subfile workbook.xml are tags <definedNames>. After deleting them, I can resave file as .xlsx and open in the excel viewer.
This file was originally excel file ("Excel_BuiltIn_Print_Area").
Some initial notes. Our exported files are correct for that document.
The problem is a MSO limitation when it comes to implementing the standard. They have an artificial limit of 32 characters for the promptTitle attribute.
I'm not sure if there is a good fix yet or if we should just consider this a Microsoft Excel bug.
Official documentation about promptTitle limitation is available at:
** Please read this message in its entirety before responding **
To make sure we're focusing on the bugs that affect our users today, LibreOffice QA is asking bug reporters and confirmers to retest open, confirmed bugs which have not been touched for over a year.
There have been thousands of bug fixes and commits since anyone checked on this bug report. During that time, it's possible that the bug has been fixed, or the details of the problem have changed. We'd really appreciate your help in getting confirmation that the bug is still present.
If you have time, please do the following:
Test to see if the bug is still present with the latest version of LibreOffice from https://www.libreoffice.org/download/
If the bug is present, please leave a comment that includes the information from Help - About LibreOffice.
If the bug is NOT present, please set the bug's Status field to RESOLVED-WORKSFORME and leave a comment that includes the information from Help - About LibreOffice.
Please DO NOT
Update the version field
Reply via email (please reply directly on the bug tracker)
Set the bug's Status field to RESOLVED - FIXED (this status has a particular meaning that is not
appropriate in this case)
If you want to do more to help you can test to see if your issue is a REGRESSION. To do so:
1. Download and install oldest version of LibreOffice (usually 3.3 unless your bug pertains to a feature added after 3.3) from http://downloadarchive.documentfoundation.org/libreoffice/old/
2. Test your bug
3. Leave a comment with your results.
4a. If the bug was present with 3.3 - set version to 'inherited from OOo';
4b. If the bug was not present in 3.3 - add 'regression' to keyword
Feel free to come ask questions or to say hello in our QA chat: https://kiwiirc.com/nextclient/irc.freenode.net/#libreoffice-qa
Thank you for helping us make LibreOffice even better for everyone!
Created attachment 166034 [details]
Example file from Calc master
So this has changed a bit in recent Excel.
Attached example file has 4 sheets on each of them a cell validation on A2 with input title, input help, error title, error message each filled with 257 characters of loremipsum.
This exported to XLSX fails to open in my 2013, indicating invalid content on each of the 4 sheets.
Reducing the length of the texts to 256 characters makes the xlsx export open in Excel.
Created attachment 166035 [details]
Example file as xlsx with 257 character long validation
Created attachment 166036 [details]
The xlsx with 257 characters long validation messages opened in Excel 13
Created attachment 166037 [details]
Example file with 256 character long validation
Created attachment 166038 [details]
Example file with 256 character long validation saved as xlsx
This opens just fine.
Hi Nisz, is this WFM now or what's left?
(In reply to Timur from comment #17)
> Hi Nisz, is this WFM now or what's left?
No, not WFM.
It is still possible to export more text for validation texts than Excel can handle original document is still bad in this regard.
Just the limits are slightly larger in 2013+ than in the documentation in comment #10 says (office.12 is 2007).
Calc / ODF can go above them so on export it is needed to cap message length to 256 characters otherwise Excel throws away the whole message (sorry for the Hungarian Excel screens).
Adjusting bug title now that we no longer aim for 2007 compatibility.
Tibor Nagy committed a patch related to this issue.
It has been pushed to "master":
tdf#84874 XLSX export: truncate validation text
It will be available in 7.1.0.
The patch should be included in the daily builds available at
https://dev-builds.libreoffice.org/daily/ in the next 24-48 hours. More
information about daily builds can be found at:
Affected users are encouraged to test the fix and report feedback.
Version: 22.214.171.124.alpha1+ (x64)
Build ID: 72056f39e01e36afac36c62988331b6813c8214f
CPU threads: 4; OS: Windows 10.0 Build 17134; UI render: Skia/Raster; VCL: win
Locale: hu-HU (hu_HU); UI: hu-HU
Thanks for fixing!