Smart service "call web service" is not pulling all results from webse

Sometimes the information you see in SoapUI does not accurately reflect the WSDL definition. I would take a look at the WSDL definition in a web browser and confirm that the relevant fields are correctly defined. For example, if "Field10" is not being populated in Appian, confirm that "Field10" is defined correctly in the WSDL in the browser and confirm that it is part of the appropriate parent element (and so on, up the chain).

Actually when I call webservice in Appian with multiple input, say it is getCustomer call that accepts customer id array as input and I send more than one customer ids , then it sends partial results, else it works fine in Appian if I send only one customer id.

Did you check the web service definition in a web browser to confirm that it is defined correctly? Also, can you please provide an example of the behavior you're seeing and the behavior you're wanting to see?

WSDL definition looks good. Example is: I expect type-A and type-B data for every customer ID, if I send only one customer ID I receive both type A and B data. If I send 4 or 5 customer ids in request, I receive type-A and TypeB data only for first id, for rest of the ids I receive type A data only. However if I try the same in soapUI, I receive both type A and type B data for all ids I am sending.

Ok, thanks for the info. I'll reach out to you separately.

Thanks @Eliot Gerson, appreciating your help.

This could indicate that the CDTs originally created by the WSDL haven't been updated to reflect the newly added fields.

To address this:

1. Identify all CDTs created that belong to this web service, sorting by namespace is usually enough
2. Delete all of them
3. Re-configure the process model using the Refresh Services button and finish configuring the node
4. Save and publish the model
5. Verify the CDTs were re-created.
6. Test again.