Linefeeds after creating XML with DOM parser

Aleksas
Member Posts: 9
Hi,
I'm tryin' to solve one problem which bothers me. I'm working with Navision Financials 2.60, and I have to build reports in xml format for Lithuanias customs.
Lithuanias custom have provided specific directions for xml document creation and it seems that MSXML4.0 DOM parser just doesn't create documents of suitable form, cause several reports already have been rejected. It seems that everything is "in one line" without any LF or CR symbols. It looks suspicious of course, cause according to W3C specification, every element has to be closed with <LF> symbol.. But when I look through the xml code in hexadecimal view, I can't find any #0A symbols (which LF stands for). Through all document which is for example 1Mb of size, there's only three #0A symbols.. I'm desperate, I tried everything and cant make DOM insert that LF symbol in the end of each element. Can anyone help me solve this problem?
I'm tryin' to solve one problem which bothers me. I'm working with Navision Financials 2.60, and I have to build reports in xml format for Lithuanias customs.
Lithuanias custom have provided specific directions for xml document creation and it seems that MSXML4.0 DOM parser just doesn't create documents of suitable form, cause several reports already have been rejected. It seems that everything is "in one line" without any LF or CR symbols. It looks suspicious of course, cause according to W3C specification, every element has to be closed with <LF> symbol.. But when I look through the xml code in hexadecimal view, I can't find any #0A symbols (which LF stands for). Through all document which is for example 1Mb of size, there's only three #0A symbols.. I'm desperate, I tried everything and cant make DOM insert that LF symbol in the end of each element. Can anyone help me solve this problem?
0
Comments
-
Try using MSXML 3.0 instead of 4.0. I have heard several say, that they have problems with 4.00
-
Actually, CR's and LF's are not defined in XML - so it is correct if it is in just one line - I once had the same problem but after checking the XML definitions, the trading partner changed the code on his side to support XML in one line (the correct way).0
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