Hi Charles, I was almost doing it  and making a directly HTTP call, but I'd found the parameter SOAPPREFIX that allow us to change it at the standard class generated by the SOAP Wizard.

If you need to do something like that, just set this parameter into the main class of the WS Client like this: Parameter SOAPPREFIX = "AnythingYouNeed"

Thank you

By the way, as ours beliefs It wasn't the problem with the message, even changing the prefix and delivery it as the manual and examples the system is rejecting the message, so we'll have to keep in touch with the support team of it.

One more time, thank you so much for your time.

Hello, Enrico, thank you so much for your time, I'm calling the WS directly from the class generated in the SOAP Wizard, we use Caché 2018.1 over here and I did a double check today in the documentation and found a parameter that solve my problem with the prefix.

If for any reason you need to change it, just set this parameter into the class generated by the SOAP Wizard.

Parameter SOAPPREFIX = "AnythingYouNeed"

I agree with you Enrico, to me It isn't the reason of the error, but I would like to try this change before waiting for a long time te answer of the government support that is really slow over here hehehe.

So, there is not a SOAP fault, the system only send a message like "malformed XML" as we forgot some tag or something else, but me and another analyst did a double check and is perfect as the documentation says.

 

Hello Enrico, so, I want to change the prefix of the Envelope, from SOAP-ENV to SOAP12 and xmlns:s to xmlns:xsd, that is the only stuff that is diferent in the request, in my mind it isn't suppose to be the reason of the rejection, but is my only difference =/.