Skip to Content
Musisz się zarejestrować, aby móc wchodzić w interakcje z tą społecznością.
Wszystkie posty Osoby Odznaki
Tagi (Zobacz wszystko)
odoo accounting v14 pos v15
O tym forum
To pytanie dostało ostrzeżenie
3 Odpowiedzi
11543 Widoki
Awatar
Ricardo Sepulveda

Hi community, I have this problem with odoo:

I installed odoo on MS Windows 2008 Server R2 and I configured the time zone correctly in my OS and Odoo Web too.

But, the problem is: when an employee let's do a check in or check out, at the database appears a wrong hour, but in the website appears good.

Example 1: A employee did a check in at 08:00 AM, but in the database appears 12:00 PM

Example 2: I create a new employee at 12:00 PM, but in the database appears 16:00 PM


How can I to repair this problem ?


Awatar
Odrzuć
Awatar
Ray Carnes
Najlepsza odpowiedź

There is no problem - this is how Odoo is designed to work.

Odoo stores ALL times and dates in UTC, not the local timezone.

It may be 12pm in Chile, but this time will be stored in the database as 4pm - because Chile is 4 hours behind UTC.

This is so Odoo can work with clients in any timezone - and they can all be correctly interpreting dates.

It also means if someone exports a file in Chile and send it to Belgium - the dates and times imported will be correct, relative to the local timezone - because the export will ALSO be in UTC.

Awatar
Odrzuć
Awatar
Landis Arnold
Najlepsza odpowiedź

Note:
Looking at the original offset of time more, it appears my fix below is for a different issue.  The 4 our offset is too great to be caused by a DayLight Savings change.  The Database would be recording UTC, not the time-zone time for the USER.  


---------

so lets strike the following that had only to do with My Odoo User Time not being reflected properly..  It did take some effort to get it "working" after the error was discovered.

Leaving it there.
----


I had this issue running just now for at least 2 days but likely since the last "Spring Forward" timechange.

Odoo should be self adjusting for this, but it did not in this situation.

My "fix" was in moving my User Timezone from America/Denver to America/Los_Angeles temporarily.  The Odoo sensed problem went away in my Odoo Header Line, and my Time Clock entries started going in on the time they should have been going in in Denver.  That was a "working tweak"...  

My Debian Server did know the correct time so that was not the issue.

I did then, reset my User Timezone back to "America/Denver", and initially the error returned in the Odoo Header but I did a few Page Reloads and the Error was finally gone.

I could not get this to kick without toggling from Denver to Los Angeles,  and then back to Denver.  No understanding of why but there seems to be a difficulty with Odoo handling systematic Time Changes such as DayLight Savings Time is my only guess.   Posting this here expecting someone else may end up looking for how to resolve a similar issue on their system.

Awatar
Odrzuć
Awatar
Hilar Andikkadavath
Najlepsza odpowiedź

See this link if you need any conversions with DateTime.

https://stackoverflow.com/questions/45915633/how-to-set-postgres-datetime-field-into-odoo-datetime-field/46010261#46010261

Awatar
Odrzuć