Hi Maitha,

I had this same problem once and solved it with a support ticket that returned me with the following information:

Allow us to share the result of our analysis on the definition you have provided:
- we verified that an error in the identification of the method is due to the fact that the code for the type "INPUT" is not being generated;
- we found that the platform has difficulty in consuming certain complex types defined "in line";
- we will consider the situation you reported so that we can improve the behavior of the platform in the future, in similar situations;
- in order to get around this situation, we replaced the definition of the complex type with an isolated definition, verifying that the error is no longer depleted;
- note that there is no need to change the WebService simply by importing the WSDL we share instead of the URL of the WebService;

At the time, I was also in a hurry and couldn't wait for support to return, so I did an Extension to consume SOAP with .Net, as a workaround.

You can use this documentation to create the Extension.

And this sample to consume a SOAP using C#

Let me know if you need any more help!

Best Regards,

Leandro.

Thanks all for your responses. I appreciate it. 

 I've resolved the compilation error (second error) by applying the work arounds in the link :

https://success.outsystems.com/Documentation/11/Extensibility_and_Integration/SOAP/Consuming_SOAP_Web_Services/Unsupported_SOAP_Use_Cases#List_Attribute_in_a_Single_List_Attribute

After I added dummy element to the complexType I am able to compile successfully. 

But the first message still appears (the optional extension element "Policy")

Great news!

This "But the first message still appears (the optional extension element "Policy")" is just a warning message, so it shouldn't be a problem.

You are welcome!