Description: I'm using a date field in the header. I formatted it several time with custom format to DD.MM.YYYY, the dates show as expected but after closing and reopening the document the fields appears as the date number. Attached an example. Steps to Reproduce: 1. Open file 2. Double click the date field 3. Additional format 4. Format Code: "DD.MM.YYYY" 5. Confirm change 6. Close file 7. Re-Open file Actual Results: Date displays as 43968 Expected Results: 17.05.2020 Reproducible: Always User Profile Reset: Yes Additional Info: Version: 6.4.3.2 (x64) Build ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8 CPU threads: 4; OS: Windows 10.0 Build 18362; UI render: default; VCL: win; Locale: en-US (en_US); UI-Language: en-US Calc: threaded
Created attachment 161040 [details] Date Format not saved
I can't confirm it with Version: 7.0.0.0.alpha1+ (x64) Build ID: 0e5e935deb0527c64865cfcc53a0421e56b74b6f CPU-Threads: 4; BS: Windows 10.0 Build 18363; UI-Render: Skia/Raster; VCL: win Locale: de-DE (de_DE); UI: de-DE Calc: CL Additional information: I guess, the datefield is the first field within the header.
Confirm on 6.4.3.2 (x64) ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8 CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; Locale: en-US (ru_RU); UI-Language: ru-RU Calc: threaded In addidtion, Internal property loses custom format but remains Date type, Custom property loses Date type and becomes numeric. Look attachment.
Created attachment 161240 [details] Date type field loses custom format in header or footer
One more addition: saving in this version of LO changes formats - earlier documents open normally, so the problem is in saving, not in loading.
(In reply to Alexander Polkhovskiy from comment #3) > Confirm on > 6.4.3.2 (x64) > ID: 747b5d0ebf89f41c860ec2a39efd7cb15b54f2d8 > CPU threads: 4; OS: Windows 10.0 Build 18363; UI render: default; VCL: win; > Locale: en-US (ru_RU); UI-Language: ru-RU > Calc: threaded Alexander, if you're able to reproduce the bug, you can change status to NEW. => NEW because of comment 3
NOT reproduced in Version: 7.2.1.1 (x64) / LibreOffice Community Build ID: 3cfc32d9754d2d239bd8ce2941029c12873010c1 CPU threads: 4; OS: Windows 10.0 Build 19041; UI render: Skia/Vulkan; VCL: win Locale: ru-RU (ru_RU); UI: ru-RU Calc: CL Can anyone else test?
(In reply to Alexander Polkhovskiy from comment #7) > Can anyone else test? ogb1966, could you please retest with an actual version of LO? => NEEDINFO
Can't confirm either with: Version: 7.2.1.1 (x64) / LibreOffice Community Build ID: 3cfc32d9754d2d239bd8ce2941029c12873010c1 CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: default; VCL: win Locale: en-AU (en_AU); UI: en-US Calc: threaded Or: Version: 7.3.0.0.alpha0+ (x64) / LibreOffice Community Build ID: 67f2a99229101757af4f40118f4d3c83ba38648b CPU threads: 8; OS: Windows 10.0 Build 19043; UI render: Skia/Raster; VCL: win Locale: en-AU (en_AU); UI: en-US Calc: threaded With three people not able to confirm in three different branches with the same OS (Windows 10), I'm going to close this as WORKSFORME. However, if ogb1966 is able to reproduce in a recent version of LibreOffice (after a user profile reset), please do reopen.
Hi, I couldn't reproduce it on a fresh install of 7.5.2. Thanks, Oren