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
- 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
Options
XMLport import error when Nodename ends twice
StFi
Member Posts: 2
Hello mibuso-members
I've got a Problem with an XML import. I get the Files from the Customers and can't change how they are.
Here's an example how the XML-Files look.
It all works when the "NotMandatory"-Field isn't empty (No.1). As soon it's empty (No.2), two closing </XMLSample>-Nodes appear and Navision gives an Error.
XMLport
(Of course the "NotMandatory" is:
minOccurs = Zero,
maxOccurs = Once)
As i said, i can't change how the XML-Files from the Customer looks, these are valid Files (XML-Validator). All works well until a "NotMandatory" isn't in the XML-File and 2 closing </XMLSample> - Node came.
I've got a Problem with an XML import. I get the Files from the Customers and can't change how they are.
Here's an example how the XML-Files look.
It all works when the "NotMandatory"-Field isn't empty (No.1). As soon it's empty (No.2), two closing </XMLSample>-Nodes appear and Navision gives an Error.
XMLport
(Of course the "NotMandatory" is:
minOccurs = Zero,
maxOccurs = Once)
As i said, i can't change how the XML-Files from the Customer looks, these are valid Files (XML-Validator). All works well until a "NotMandatory" isn't in the XML-File and 2 closing </XMLSample> - Node came.
0
Best Answer
-
StFi
Member Posts: 2
Hello mibuso-members
I've found the solution (even if it's a strange one).
As soon i changed the "MaxOccurs"-Property of the intended XMLSample to "Unbounded" it worked.
If someone has a better workarround i'll be happy.
(Because the intended XMLSample should be MinOccurs / MaxOccurs = once)0
Answers
I've found the solution (even if it's a strange one).
As soon i changed the "MaxOccurs"-Property of the intended XMLSample to "Unbounded" it worked.
If someone has a better workarround i'll be happy.
(Because the intended XMLSample should be MinOccurs / MaxOccurs = once)