I saw that the date in the database does not match the date in the GUI depending on seconds of the timestamp in database. Could reproduce on PPM 126.96.36.199 09 11 and PPM 188.8.131.52 01 51
For Example in inv_investments:
DB: schedule_finish: 2020-12-31 00:00:00.000
End Date in GUI: 30.12.2020
I would expect in GUI to see 31.12.2020
If you just add one seconde in DB it shows the correct value:
schedule_finish: 2020-12-31 00:00:01.000
End Date in GUI: 31.12.2020
As the projects are imported with just dates and added with 00:00:00.000 as time, it delivers wrong dates for the endusers in the GUI. Is this expected behavior? Or do we have to change the import and keep this in mind for any other date fields, which might be act like this.
If you change the date field manually in the GUI, then the time 17:00:00.000 will be added automatically and the date field is correct.
On the other hand for the schedule_start it seems to work correctly.
DB: schedule_start: 2020-01-01 00:00:00.000
Start Date in GUI: 01.01.2020
DB: schedule_start: 2020-01-01 23:59:59.000
If you change the start date field manually in the GUI, the the time 08:00:00.000 wil be added automatically.
Is this normale behaviour? Or a bug which needs to be adressed to support?
We have to recheck all the finish_dates now to add a second, when the time is 00:00:00.000. And don't know which date fields are affected as well.
Thanks for any response
This is expected behavior see the explanation here https://comm.support.ca.com/kb/on-my-report-the-finish-date-is-showing-one-day-later-than-in-the-gui-why/kb000024259