Time Zone Conflict

(0) Share

Report

Posted on by Community Member

Dear Team,

I need to know about the time zone conflict which happened in ax 2009. and how it is rectified in ax 2012 R3.

Basic Example: Workflow approval

Originator is from India sending the approval on 30/3/2017 and the approval person is from USA so he would be getting the approval on 29/3/2017 so this date conflict was a problem in ax 2009 and this was solved in ax 2012 R3.

1. Needed to know on what basis it was solved.

2. Wanted to know if there were any other conflict regarding time zone in ax 2009 which is solved later in ax 2012 R3.

Thanks

Suresh

*This post is locked for comments

I have the same question (0)

All responses (6)

Answers (0)

Community Member on at

Like (0)

Report

RE: Time Zone Conflict

Any Suggestions!

Thanks

Suresh

Was this reply helpful? Yes No
Suggested answer

guk1964 10,888 on at

Like (1)

Report

RE: Time Zone Conflict

Yu may need a separate Aos for each time one- see this note from Technet

Time Zones and Dates

Some fields in Dynamics AX contain information about dates, some fields contain information about time, and some fields contain information about both. The fields that contain both use UTC. UTC supports multiple time zone capabilities running server-based code. The fields that only contain date information or only contain time information do not have time zone capabilities. An example of a field that does not have time zone capabilities is the Invoice Date. Invoice Date extends a date type, carries no time information, is not based on UTC, and has no time zone capabilities. If you are using a field that does not have time zone capabilities and you need it to work across multiple time zones and you require transaction-level posting with the local date and time, then you must set up an AOS in each time zone. If you do not setup a separate AOS for each time zone, then the posting date will be reflected by the time zone which the AOS is associated not the local time zone. For example, if your AOS is based in Greenwich Mean Time (London) and a subsidiary of your company is based in the Central Time Zone (Chicago), the time difference is usually 6 hours behind. Any transaction that is posted after 6:00 PM in Chicago will be recorded as a transactional date for the following day, thus you will have an incorrect posting date based on local time zone.

Also see this nice write up from Bill Thompson:

https://stoneridgesoftware.com/working-with-utcdatetime-functionality-in-dynamics-ax-2012/

If you get this error The internal time zone version number stored in the database is higher than the version supported by the kernel (8/7). Use a newer Microsoft Dynamics AX kernel then this is caused when you start the service after restoring the database from DB from one system to another due to mismatch of the time zone in the AX system. This error is in the event log. Open SQL 'SQLSystemVariables' table and edit the record in 'SYSTIMEZONEVERSION' column from 8 to 7.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Time Zone Conflict

Hi magic1949,

Thanks for the reply but what am asking is whether ax 2009 had a bug with time zone conflicts. In 2012 base product there are no issue's , so now my question is whether it was a bug which was resolved via hotfix or on a version upgrade.

Thanks

Suresh

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Time Zone Conflict

HI Crispin,

On a functional point of view, even Ax 2009 has timezone which can be set for specific user as like in ax 2012. So in 2012 workflow approval process happens via timezone mentioned. since 2009 also has timezone specific at user level. why was there a timezone conflict .

For example,

Workflow originator - India

Workflow Approval - USA.

As per the example India GMT is (+5.5) where USA GMT is (-4). so now i guess you understand my point. GMT Differs so Ax 2009 was not able to attach to future date and day behind as per GMT.

Thanks

Suresh.

Was this reply helpful? Yes No
Community Member on at

Like (0)

Report

RE: Time Zone Conflict

Any suggestions Please!

Was this reply helpful? Yes No
André Arnaud de Cal... 299,386 Super User 2025 Season 2 on at

Like (0)

Report

RE: Time Zone Conflict

Hi Suresh,

You tried to contact me offline and I had some initial basic questions before really understanding your issue. The answer from magic1949 is correct here. UTCdatetime fields were introduced in AX2012; replacing separate fields for a date and a time. This UTCdatetime field is always storing the date/time in the database converted from the user timezone to Greenwich Mean Time(GMT =UTC 0). When displaying the date/time field; it will present it in the timezone of the user. Thanks to the new field type this issue has been solved in AX2012, but cannot be done in AX2009 without customizations. If you need to present the date and/or time in the timezone of the user, you should store additional information in the table about the used timezone.

Was this reply helpful? Yes No