FORUM PLAN UPDATE: Date revision: This forum will remain open to new posts and responses until December 1, 2018. (After that date, you will still be able to view and search the forum.) Also, we're taking a second look at the best place to host future conversation. For now, keep using this forum, and stay tuned for more news.
RE: @created returns the creation date of the document Harkpabst Meliantrop 3.Aug.18 05:33 AM a Web browser Domino Designer All ReleasesAll Platforms
Nana, Carl really gave you all the information you need. Everything will work if you follow his advice closely. Maybe one more note to make it perfectly clear:
Domino does already store the creation date of each document without you having to program anything. The date is saved inside the document and @Created is the function to retrieve this system generated date-time-value.
Adding a "computed when composed" field to a form does NOTHING for documents that already existed before the field was added. As Carl suggested, use the properties window for the documents in question to see what the system generated Created date is (first tab) and which fields are actually stored in the document (second tab). New "computed when composed" field are NOT part of the document, unless the document is actively saved. Once the document has been saved after adding the new field, it will contain the correct value, if you use @Created.
Still there is usually no need to add such a field yourself. You can use @Created in view column formulas directly. For display on the form you can use a "computed for display" field or computed text (computed value). The only exception to this rule could be complex and/or distributed workflow applications where the content of existing documents might be copied to new documents which are then saved. Such application logic should be strictly avoided, if possible. Even if documents are replicated from other servers in a distributed environment, @Created will still return the date on which the document was originally created in the original database.
Also date-time values can be formatted for display in any way you like, so there is no advantage in storing them as text (but there are many disadvantages). In a view column you can use the column properties to chose from different display formatting options. In a computed for display field (or computed text) you can use @Text to format the date as needed.
I hope this did not add further confusion but made the point more clear. :)