WHAT IS THE BUG The ‘Creation date’ value is not correct. For example, I’m creating a new object today (Dec 25) but the Creation date value is Dec 13. [image] THE EXPECTED BEHAVIOR After I create a new object, the ‘Creation date’ value is correct for both date & time. ADDITIONAL CONTEXT I ju…

This report has been added to our issue tracker and received by the Development Team.

Update: I think this bug related to my template since the template created on Dec 13, 2023 [image]

Thank you @Angelo !! :crossed_fingers:

Hi, having the same issue in 37.3 with Creation Dates. The creation date of a new object is inheriting the Creation Date of the template (in my case this was Aug 10, 2023 and the object was Project). This is not happening on all custom templates, for example I have a Task template working as expecte…

This bug is one good reason more for implementing what I suggested here: [image] Custom Sort Date Relation to override Creation Date Feature Requests WHAT DO YOU RECOMMEND Surely we all know the problem: sometimes it would become handy (or there is even urgent…

Found this bug when testing some Experiences. New objects created from the default object template has the same creation date, not today’s date. If a new object is created from a blank template, it correctly shows today’s date.

Same issue here. When creating a new object, the creation date will be derived from the template’s creation date, but not every time (sometimes the creation date will be correct).

Any news on that bug? I’ve got it when I create a note from a new note template (the creation date is good with the blank template). It’s very annoying. Especially because it’s not possible to edit the creation date

Agree, the bug is not fixed yet, I have the same problem.

I still confront this issue today. I use template form gallery and the objects created have old creation dates not the one of today (or the day it was created). It makes it annoying to sort things out because have to find a work around filter.

This issue has been fixed by the Development Team and will be implemented in an upcoming release.

The 'Creation date' value is not correct

Bug Reports Closed

Code-Jack January 2, 2024, 2:28pm 6

This bug is one good reason more for implementing what I suggested here: