Howdy, Stranger!
Categories
- All Categories
- 73 General
- 73 Announcements
- 66.5K Microsoft Dynamics NAV
- 18.5K 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
- 267 Dynamics CRM
- 109 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 992 SQL General
- 384 SQL Performance
- 33 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
- 259 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions
Options
Web Service Culture
ldreamsl
Member Posts: 33
With reference to what is written
http://blogs.msdn.com/b/nav/archive/201 ... uage.aspxb
There is a solution to solve the problem without sacrificing the hotfix?
Thanks.
http://blogs.msdn.com/b/nav/archive/201 ... uage.aspxb
There is a solution to solve the problem without sacrificing the hotfix?
Thanks.
God does not play dice with the universe. [Albert Einstein]
0
Comments
Are you facing the problems discribed in the KB, or do you have problems with the Dateformat after applying the hotfix?
After applying the hotfix, the Web Service uses only the culture en\US. And this is valid for all following hofix. Is there a solution to use the culture it\IT with Web Service?