<soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:tes="urn:microsoft-dynamics-schemas/codeunit/TestWebService" xmlns:x70="urn:microsoft-dynamics-nav/xmlports/x70050"> <soapenv:Header/> <soapenv:Body> <tes:TestFunction1> <tes:testXMLPort> <!--Zero or more repetitions:--> <x70:TestTable> <!--Optional:--> <x70:Nr>0</x70:Nr> </x70:TestTable> </tes:testXMLPort> </tes:TestFunction1> </soapenv:Body> </soapenv:Envelope>
<s:Envelope xmlns:s="http://schemas.xmlsoap.org/soap/envelope/"> <s:Body> <s:Fault> <faultcode xmlns:a="urn:microsoft-dynamics-schemas/error">a:Microsoft.Dynamics.Nav.Types.Exceptions.NavNCLXmlPortUnexpectedElementException</faultcode> <faultstring xml:lang="de-DE">The Element <x70:TestTable> is unexpected.</faultstring> <detail> <string xmlns="http://schemas.microsoft.com/2003/10/Serialization/">The Element <x70:TestTable> is unexpected.</string> </detail> </s:Fault> </s:Body> </s:Envelope>
x70:from the request. But, up to now, that is not possible in the original request.
Answers
something like...
[Build lautXmlStyleSheet]
XmlSourceDocument.transformNodeToObject(lautXmlStyleSheet, XmlDestinationDocument);