Linefeeds after creating XML DOM

Skeeve
Member Posts: 33
Hi All,
well, there doesn't seem to be much traffic in this category but I'll try it anyway <img border="0" title="" alt="[Wink]" src="images/smiles/icon_wink.gif" />
I'm currently implementing Commerce Gateway for a client who will connect his Financials 2.65 to a vendor's SAP system.
So I mapped Navision's PO XML schema to SAP IDOC which works just fine.
My only problem here is that Navision doesn't create linefeeds while creating the XML DOM.
So the finished XML document goes through to MS BizTalk Server without linefeeds and the resulting SAP IDOC Document also doesn't have linefeeds.
Unfortunately the vendor must have linefeeds in order to being able to process the document.
Anybody any ideas on that one?
thanks,
Skeeve (mailto:tb@astongroup.de)
well, there doesn't seem to be much traffic in this category but I'll try it anyway <img border="0" title="" alt="[Wink]" src="images/smiles/icon_wink.gif" />
I'm currently implementing Commerce Gateway for a client who will connect his Financials 2.65 to a vendor's SAP system.
So I mapped Navision's PO XML schema to SAP IDOC which works just fine.
My only problem here is that Navision doesn't create linefeeds while creating the XML DOM.
So the finished XML document goes through to MS BizTalk Server without linefeeds and the resulting SAP IDOC Document also doesn't have linefeeds.
Unfortunately the vendor must have linefeeds in order to being able to process the document.
Anybody any ideas on that one?
thanks,
Skeeve (mailto:tb@astongroup.de)
0
Comments
-
Hello
I know that this answer may not will help you very much, but I will write it anyway just to descripe the principles of XML formatting for transport of data via the internet.
If you want to send an XML document to someone it is your responsibility to ensure that the your XML-document is formatted according to the recommendations of W3C.
Since I do not belive, that the XML-documents Navision have developed do not apply to these standards I would say that it is the SAP-system that is not working according to the standard recommendations.
If the recieving system need another format than the one formattet accordin to the standard recommendations it is their own responsibility to make the transformation of the document to fit their specific needs before. For this purpose XSL and XSLT has been created and I suggest that they start to use these tools themselves instead of forcing you to send a document that is not formatted according to the recommendations.
But perhaps this is not a posssibility.0 -
Thanks for your input and guess what. Of course you're absolutely right. Since our customer's partner (using SAP) already successfully connected CocaCola to their system I was of the opinion that they seem to be able to handle everything correctly.
But that was not the case. Coke also uses SAP and they send a document including linebreaks.
To make a long story short: Our cutomers's partner DID change his own scripts in order to being able to process STANDARD xml docuements WITHOUT linebreaks :-)
thanks again,
Skeeve0
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