Description: This happend once before and now it is happening again only Worse. Inser Fixed Date no longer fixed. It is now current date. I keep a log in a single Writer document of am event that takes place MOST Sundays. For each Sunday's event I have a page break followed by one space and the date created by <Insert><Field><More Fields>[Type=Date,Select=Date (fixed),Format=Friday, December 31, 1999]. This morning when I opened my document EVERY "fixed date" was last weeks (the last time I updated the document) date. I added todays entry and saved the file and when I re-opened the document all the dates were todays date. Steps to Reproduce: 1.Create a document with a fixed date using the <Insert><Field><More Fields> fixed date. 2.Wait a couple of days. 3.Open the document Actual Results: Fixed date becomes current date. Expected Results: Fixed date remains a date in the past. Reproducible: Always User Profile Reset: No Additional Info: User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64; rv:53.0) Gecko/20100101 Firefox/53.0
We need a sample. Please copy your file and redact anything sensitive, then save as Flat ODF--.fodt and post. We need to look at the XML fielding. It should be in a Text:Date stanza, with text:date-value="[date]" and must include a text:fixed="true". So look something similar to this: <text:p text:style-name="Standard"><text:date style:data-style-name="N84" text:date-value="2017-04-30T11:47:47.261999705" text:fixed="true">2017-04-30</text:date></text:p>
@Steve, I received the screen clips via DropBox, can't do anything with them. Please attach the document, or a redacted sample. The Ctrl+F2 field editing applies specific formatting when the Date is Fixed. We need to see if that is being applied in your problem document.
@Steve, the "round trip" from ODF document with Date (Fixed) field does not survive the ww8 filter export to .DOC nor reimport to ODF. The OOXML .DOCX format does. The obvious thing is to NOT use .DOC or OOXML format, and if you need to share the document do it in PDF. Duplicating this to your still open issue. *** This bug has been marked as a duplicate of bug 100961 ***