Character map on XML import

MSBP
Member Posts: 17
Hey.
I have a XML import that imports XML documents via. COM object.
The XMLPort is set to handle UTF-8 format, yet Navision reads this as ANSI which gives me æøåÆØÅ as #|$[]\ and I then need to reconvert it back to æøåÆØÅ.
XMLfile has letters in it as éüä ect. which in turn is read as ?
How do I handle the XML Doc or reconvert my characters whitout using CONVERTSTR :?
It is a NAS that handles the COM objects, can i eventually set this up somewhere ?
I have a XML import that imports XML documents via. COM object.
The XMLPort is set to handle UTF-8 format, yet Navision reads this as ANSI which gives me æøåÆØÅ as #|$[]\ and I then need to reconvert it back to æøåÆØÅ.
XMLfile has letters in it as éüä ect. which in turn is read as ?
How do I handle the XML Doc or reconvert my characters whitout using CONVERTSTR :?
It is a NAS that handles the COM objects, can i eventually set this up somewhere ?
Dynamics NAV L337
0
Comments
-
If you use XMLPort, XMLPort will automatically format the characters from NAV into UTF and backup during export/import. Can you be more specific, how you are using the COM in connection with the XMLPort? I think that the problem will be in the COM...0
-
The COM is a dll designed inhouse which is using messageque MSMQ to deliver the XML file into the XMLPort that imports it into Navision.
The XML Document holds é æ ø Å etc. but as soon at the XMLPort grabs the information it is translated into ANSI which then is ? in many cases, ]/ etc.Dynamics NAV L3370 -
All depends on under which codepage you are running the NAV client. If it is some codepage which do not understand these characters, they will be miss-converted. The XMLDom is UTF-enabled, NAV is not. The translation is done based on the codepage for non-unicode applications of the Windows system.0
-
I suspected that the Codepage was the main issue here ...
I Use XMLDom before sending the XML into the XMLPort ... is it possible to use some commandset in the XMLDom to "transform" my XML document befor importing it in order to avoid the Codepage problem ?Dynamics NAV L3370 -
kine wrote:All depends on under which codepage you are running the NAV client. If it is some codepage which do not understand these characters, they will be miss-converted. The XMLDom is UTF-enabled, NAV is not. The translation is done based on the codepage for non-unicode applications of the Windows system.
Would it help to convert the XML into the Codepage used by Navision before sending it into Navision using the MSMQ ?Dynamics NAV L3370
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
- 116 Navision DOS
- 851 Navision e-Commerce
- 1K NAV Tips & Tricks
- 772 NAV Dutch speaking only
- 617 NAV Courses, Exams & Certification
- 2K Microsoft Dynamics-Other
- 1.5K Dynamics AX
- 320 Dynamics CRM
- 111 Dynamics GP
- 10 Dynamics SL
- 1.5K Other
- 990 SQL General
- 383 SQL Performance
- 34 SQL Tips & Tricks
- 35 Design Patterns (General & Best Practices)
- 1 Architectural Patterns
- 10 Design Patterns
- 5 Implementation Patterns
- 53 3rd Party Products, Services & Events
- 1.6K General
- 1.1K General Chat
- 1.6K Website
- 83 Testing
- 1.2K Download section
- 23 How Tos section
- 252 Feedback
- 12 NAV TechDays 2013 Sessions
- 13 NAV TechDays 2012 Sessions