Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.6K Microsoft Dynamics NAV
- 18.7K NAV Three Tier
- 38.4K NAV/Navision Classic Client
- 3.6K Navision Attain
- 2.4K Navision Financials
- 115 Navision DOS
- 854 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 615 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 304 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 993 SQL General
- 384 SQL Performance
- 34 SQL Tips & Tricks
- 34 Design Patterns (General & Best Practices)
- Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.7K General
- 1.1K General Chat
- 1.6K Website
- 79 Testing
- 1.2K Download section
- 23 How Tos section
- 260 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
NAV 2013 web service time zone issue
CSide
Member Posts: 7
Hi all,
I wondered if anyone experienced the following issue in the past and if so maybe someone knows how to solve it.
I'm calling a NAV web service from a .NET application. The NAV web service is a page broadcasted together with a codeunit (they have the same web service name but the codeunit is not "published").
Sending data to the web service runs fine but we noticed that datetime fields are not stored correctly in NAV. In fact the time value displays 2 hours later than the value sent form the .NET application.
I know about the "ServicesDefaultTimeZone" in the CustomSettings.config and put that to "Server Time Zone". So now NAV receive CEST (UTC + 2) from the external application and should store UTC in the SQL database. The RTC client should then also show UTC + 2 (See http://blogs.msdn.com/b/nav/archive/2011/01/11/time-zones-usage-in-microsoft-dynamics-nav-web-services.aspx).
I tried everything but the NAV 2013 web service is still seeing the time I send as UTC.
I restarted the service, restarted the server, modified all other NAV services on the same server (including 2009 R2)...unfortunately nothing works.
Monitoring the outgoing web service call in my .NET application learned that it is sending the correct times.
I also tried it on my local PC and I get the same result. Tests on NAV 2009 R2 showed that it is actually working on that version.
Anyone an idea ? Or does anyone know if this is a known bug in NAV 2013 ?
Thank you very much in advance.
Kind regards,
Tom T.
I wondered if anyone experienced the following issue in the past and if so maybe someone knows how to solve it.
I'm calling a NAV web service from a .NET application. The NAV web service is a page broadcasted together with a codeunit (they have the same web service name but the codeunit is not "published").
Sending data to the web service runs fine but we noticed that datetime fields are not stored correctly in NAV. In fact the time value displays 2 hours later than the value sent form the .NET application.
I know about the "ServicesDefaultTimeZone" in the CustomSettings.config and put that to "Server Time Zone". So now NAV receive CEST (UTC + 2) from the external application and should store UTC in the SQL database. The RTC client should then also show UTC + 2 (See http://blogs.msdn.com/b/nav/archive/2011/01/11/time-zones-usage-in-microsoft-dynamics-nav-web-services.aspx).
I tried everything but the NAV 2013 web service is still seeing the time I send as UTC.
I restarted the service, restarted the server, modified all other NAV services on the same server (including 2009 R2)...unfortunately nothing works.
Monitoring the outgoing web service call in my .NET application learned that it is sending the correct times.
I also tried it on my local PC and I get the same result. Tests on NAV 2009 R2 showed that it is actually working on that version.
Anyone an idea ? Or does anyone know if this is a known bug in NAV 2013 ?
Thank you very much in advance.
Kind regards,
Tom T.
0
Comments
The ServicesDefaultTimeZone parameter fixed this issue when I encountered it, but only for one timezone. It becomes more complicated when you have users in different timezones connected to the same database :?
I suggest that you use the management console instead of manually editing the CustomSettings.config file, especially if you're not using the default instance.
My config file contains this line:
<add key="ServicesDefaultTimeZone" value="Server Time Zone" />
And of course this modification requires a restart of the NAV service.
Best regards,
François
I think your best option is to store your dates as Unix Timestamps, which are just integers.