Date field in LO Draw [CLOSED]

v 6.3.4.2
The date field gives the last date opened, with no option to insert the date last modified. This option is catered for in LO Writer, but I cannot find it in Draw.
I’d have thought most people would want the date modified.
Is there any way to achieve this?

Draw hasn’t a sound concept of the textfield service. Basically texts in Draw support textields as content, but the relevant type DateTime e.g. is implemented inconsistently: com.sun.star.text.textfield.DateTime has a property .NumberFormat, but Draw doesn’t support NumberFormats in an appropriate way. The funny selection you get offered when inserting a date via the menu will tell you what I mean.
Anyway: Even the full-grown dialog for inserting fields in Writer doesn’t offer the insertion of the DateTime of last modification, but only “fix” and “variable” where “fix” may be used to get a workaround if modification shall be documented. (See comment below.)
In Writer (NOT in Calc), however, you can create textfields for the purpose resorting to user code. In Draw you can’t for the reason I already mentioned.
Considering to use a “macro” accessing the DocumentProperties where information about the last modification is kept, you should therefore omit the textfield service and instead use textboxes with DateTime values reasonably formatted to string representation.

[Edit 2020-02-22 about 23:40 UTC: Replace buggy attachment with the correct one. See comment below.]
See this attached example for more detail.
[End edit]

If you decide to use the macros (or a similar implementation) contained there, you should complete it by a few checks, and save it then to a module of your local Standard library.

Thanks for the explanation. I suppose it’s not a big dela to manually enter a date each time I modify it.

(In Writer, under Insert>fields>more fields there is a menu header 1Docinformation’ where you can enter date modified. It seems to work OK).

Thanks for your comment and the hint concerning DocIndformation. I had forgotten about it.
The comment notification also gave me an opportunity to look a second time into the code conatained in the original attachment. There was a serious error: Instead of the appropriate DateSerial function of Basic I had misused the Date “statement” of Basic which is completely different and should be avoided.
I will edit the answer and replace the bad attachment with the correct one.