Here's the xmlport definition(it's very long, i post just a snippet)Multiple definition of element 'OrderResponse:SpecialInstructions' causes the content model to become ambiguous. A content model must be formed such that during validation of an element information item sequence, the particle contained directly, indirectly or implicitly therein with which to attempt to validate each item in the sequence in turn can be uniquely determined without examining the content or attributes of that item, and without any information about the items in the remainder of the sequence
SpecialInstructions InstructionTypeReferenceInformation ReferenceInformation ReferenceType DocumentReference DocumentIdentifier DateTime DateTimeQualifier SpecialInstructions InstructionTypeactually, the problem is obviously the double "SpecialInstructions" Element at the same indentation level. In my opinion, it's not correct, but as i said, the xmlport works fine in classic but does not work if exposed as webservice.
Comments
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.