Communicating with RoleTailored Clients in Different Time Zones
Microsoft Dynamics NAV Server can interact with RoleTailored clients in different time zones.
The content in this topic only applies to Microsoft Dynamics NAV 2009 SP1. For Microsoft Dynamics NAV 2009 content, see Developer and IT Pro Help for Microsoft Dynamics NAV 2009.
If the client data contains data of the type DateTime, then upon receiving the data from the client, Microsoft Dynamics NAV Server converts this data into Coordinated Universal Time (UTC) based on the client time zone. When passing data of type DateTime back to the client, Microsoft Dynamics NAV Server converts the time back to the local time zone of the client before presenting the data to the end user.
Different countries and regions sometimes have different rules for determining when and if to start and end Daylight Saving Time. If computers running Microsoft Dynamics NAV Server computers are kept current with Windows updates, then changes to Daylight Saving Time are managed automatically.
There is limited support for reading and writing in UTC in the RoleTailored client. Specifically, the client evaluates and formats DateTime values in forms and pages using format code 9. This format is UTC but can be difficult to read. For example, the format is 2008-01-01T10:22:00Z.
Web Services Originating from Different Time Zones
Microsoft Dynamics NAV Server cannot determine the time zone of origin for a Web service. Therefore, all Web server communication should be in UTC. All business logic is executed with respect to UTC.