Hi Danielle,
> The problem was the the object was not defined in the WSDL, but it was still required [...]
OK, thank you for the details.
If I got you correctly, it looks like the problem was not with TestComplete, but with the tested web service. The case is that neither TestComplete nor any other web service client has no other means to get the information about methods and data types required by the web service but from the published WSDL. And if WSDL lacks some information, this means that any client will not be able to communicate with this web service.
I think that it is worth to talk to developers and figure out why this information was not published in the WSDL file. As of now, for me this looks like a problem (issue) in web service.
