<?xml version="1.0"?> <soap:Envelope xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"> <soap:Body> <BarcodePrintZpl> <user>testuser</user> <variablesString>testvars</variablesString> <filepath>testfile</filepath> <printerName>testprinter</printerName> </BarcodePrintZpl> </soap:Body> </soap:Envelope>
<?xml version="1.0" encoding="utf-8"?> <soap:Envelope xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xmlns:xsd="http://www.w3.org/2001/XMLSchema" xmlns:soap="http://schemas.xmlsoap.org/soap/envelope/"> <soap:Body> <BarcodePrintZpl xmlns="http://tempuri.org/"> <user>string</user> <variablesString>string</variablesString> <filepath>string</filepath> <printerName>string</printerName> </BarcodePrintZpl> </soap:Body> </soap:Envelope>
Answers
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Zaid Tariq
Dynamics NAV/365 BC Developer at Dynamics 360
please like / agree / verify my answer, if was helpful.
Anyway, stick to the schema given by the WSDL document, including namespaces, and use the proper methods, parameters or properties for namespaces. Don't define them as attributes, unless you create the whole request as text.