Are you experiencing problems when using advanced SOAP XML payloads in “Invoke Web Services”?

I did! it seems to work properly, but some parameters did not get filled correctly.

After some testing i discovered that the parameters in the XML payload has to be in the correct order!!

If not, the parameters “in between” will be filled by NULL, and then later it will ignore or skip the rest of the parameters if they appear in the wrong order!!

The reason is that it is using the DataContractSerializer.

thanks to by colleague Claus for finding this forum thread there they discuss the challenge: