KB-1258 Some or all CDTs are not created after invoking Call Web Service smart service or webservicequery() function

Nick Vigilante — Tue, 07 Mar 2017 14:56:26 GMT

Current Revision posted to Appian Knowledge Base by Nick Vigilante on 3/7/2017 2:56:26 PM

Symptoms

Invoking the Call Web Service smart service or the webservicequery() function does not create or recreate all the relevant CDTs in the environment.

Cause

There are two possible causes:

If this is the first time this WSDL was used on this environment, then this may be because one or more elements in the WSDL are not properly qualified.
If this is not the first time, then this can be caused due to caching of the old datatypes that the WSDL previously generated.

Action

For WSDLs in general, when the elementFormDefault parameter is set to qualified, all elements need to be defined by their fully qualified name, which is <namespace>:<name>. Alternately, the elementFormDefault can be set to unqualified to avoid this validation. This should resolve the issue if it was a first time occurrence.

On the other hand, if this is caused due to the caching of old data types then follow the steps below:

Make sure all relevant CDTs for the WSDL are deleted.
Re-invoke the web service to recreate the CDTs.
If the CDTs are still not recreated, then restart the application server to clear the data type cache and then re-invoke the web service.

Affected Versions

This article applies to all versions of Appian.

Last Reviewed: March 2017

Tags: CDTs, third-party, web services, application design