Bug 54831 - Custom (and other) properties not saved to MS XML formats
Summary: Custom (and other) properties not saved to MS XML formats
Alias: None
Product: LibreOffice
Classification: Unclassified
Component: LibreOffice (show other bugs)
(earliest affected)
3.5.4 release
Hardware: Other Linux (All)
: medium major
Assignee: Not Assigned
Depends on:
Reported: 2012-09-13 00:43 UTC by tom
Modified: 2016-10-12 00:07 UTC (History)
1 user (show)

See Also:
Crash report or crash signature:


Note You need to log in before you can comment on or make changes to this bug.
Description tom 2012-09-13 00:43:34 UTC
When saving a file to MS XML format (tested with .docx and .xlsx) properties are removed from the document.

Steps to reproduce:

1. Create new spreadsheet
2. File > Properties > Custom Properties
3. Add new custom property
4. Save file as test.xlsx
5. Click 'Use Microsoft Excel 2007/2010 XML Format'
6. Quit LibreOffice
7. Open test.xlsx
8. File > Properties > Custom Properties
9. Observe missing properties
Comment 1 A (Andy) 2012-12-27 20:17:04 UTC
reproducible with LO (Win7 Home, 64bit)
Comment 2 philip.louw 2013-06-27 08:22:01 UTC
Reproduced with LibreOffice or
Also found:
1.  Create spreadsheet with Microsoft Office
2.  Add custom Properties
3.  Save and Exit
4.  Open in LibreOffice edit a cell and save.
5.  This clears all Custom Properties
Comment 3 eugen.krizo 2014-11-28 13:40:48 UTC
Reproduced with LibreOffice Writer / Linux Mint
Comment 4 alessio_d 2015-08-11 11:22:12 UTC
Reproduced with LO Calc / Win7 x64
The bug is old, is there any chance that it will be fixed?
Comment 5 QA Administrators 2016-09-20 10:21:54 UTC Comment hidden (obsolete)
Comment 6 tom 2016-10-12 00:07:29 UTC
Build ID: 31dd62db80d4e60af04904455ec9c9219178d620
CPU Threads: 4; OS Version: Mac OS X 10.12; UI Render: default; 
Locale: en-AU (en_AU.UTF-8); Calc: group

Going through the steps now saves the custom properties.

Note that I can't verify that the exact issue described in [https://bugs.documentfoundation.org/show_bug.cgi?id=54831#c2](Comment 2) has been fixed, as I don't have a copy of MS Office to check with.