User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:46.0) Gecko/20100101 Firefox/46.0 Build Identifier: LibreOffice 5.1.2.2 When I save a sheet in xlsx format it doesn't retain some of the cell formatting. I.e. cells that are saved with a numeric value with two decimal point revert to no decimals when I reopen the file. Reproducible: Always Steps to Reproduce: 1. save file 2. reopen file 3. change formatting 4. save file again 5. etc. etc. Actual Results: Results are always the same: formatting is lost Expected Results: I would expect that simple number formatting would be retained [Information automatically included from LibreOffice] Locale: en-US Module: SpreadsheetDocument [Information guessed from browser] OS: Windows (All) OS is 64bit: yes Reset User Profile?No
Hello, Thank you for filing the bug. Please send us a sample document, as this makes it easier for us to verify the bug. I have set the bug's status to 'NEEDINFO', so please do change it back to 'UNCONFIRMED' once you have attached a document. (Please note that the attachment will be public, remove any sensitive information before attaching it.) How can I eliminate confidential data from a sample document? https://wiki.documentfoundation.org/QA/FAQ#How_can_I_eliminate_confidential_data_from_a_sample_document.3F Thank you
Created attachment 124872 [details] little test sheet I found the same problem when saving as .xls
I attached a tiny test sheet. Should mention that the same problem occurs when trying to save in .xls, so formatting gets lost both in .xls and .xlsx
Hi Roberto We need the original ODS first - then we'll save it on our side to see what formatting is lost. It doesn't help to just show us a post-damaged file. Moving back to NEEDINFO. Thanks
Created attachment 124887 [details] test file The reason why I only included the .xlsx file is because that is the file that is giving the problem. Column A is date format yyyy-mm-22 and column B is number format with two decimals. I can repeatedly set these formats but every time I open the file the number format has changed to "no decimals". Actually sometimes the date format also changes, but I cannot consistently repeat that. Although the file started out originally as an .ods it has for quite a while been just an .xlsx, the reason being that is located in my Dropbox and in .xlsx format it can more easily be read on other devices such Chromebook or my phone.
I don't know, I just wrote a comment in the previous screen. Here it is again: The reason why I only included the .xlsx file is because that is the file that is giving the problem. Column A is date format yyyy-mm-22 and column B is number format with two decimals. I can repeatedly set these formats but every time I open the file the number format has changed to "no decimals". Actually sometimes the date format also changes, but I cannot consistently repeat that. Although the file started out originally as an .ods it has for quite a while been just an .xlsx, the reason being that is located in my Dropbox and in .xlsx format it can more easily be read on other devices such Chromebook or my phone.
No repro with 5.1.2,win7. Format 0,00 stay the same after save and reopen.
No repro. Maybe try https://wiki.documentfoundation.org/UserProfile#Resolving_corruption_in_the_user_profile 64-bit, KDE Plasma 5 Build ID: 5.1.2.2 Arch Linux build-1 CPU Threads: 8; OS Version: Linux 4.5; UI Render: default; Locale: fi-FI (fi_FI.UTF-8)
Roberto, please try to reset profile as mentioned in comment 8 and let us know.
Thanks for the suggestion to reset profile. I tried it, and it makes no difference whatsoever.
Thank you for reporting the bug. I can not reproduce the bug in Version: 5.3.1.2 (x64) Build ID: e80a0e0fd1875e1696614d24c32df0f95f03deb2 CPU Threads: 4; OS Version: Windows 6.19; UI Render: default; Layout Engine: new; Locale: en-US (en_US); Calc: group
@roberto please retest with latest LibO 5.3.2.2 and tell if issue persists. I set status to NEEDINFO revert it to UNCONFIRMED if bug is still there or change it to RESOLVED WORKSFORME if bug is gone
Sorry folks, I haven't paid much attention to this for a while. I just tried with version 5.2.3.3 and the bug appears to be gone. Thank you all.