Appian Community
Site
Search
Sign In/Register
Site
Search
User
DISCUSS
LEARN
SUCCESS
SUPPORT
Documentation
AppMarket
More
Cancel
I'm looking for ...
State
Verified Answer
+2
person also asked this
people also asked this
Replies
6 replies
Subscribers
7 subscribers
Views
2925 views
Users
0 members are here
Share
More
Cancel
Related Discussions
Home
»
Discussions
»
Integrations
We are having an issue with the webservicequery() function where the function cl
mikej117
over 9 years ago
We are having an issue with the webservicequery() function where the function claims that the called web service method is not available. The method is infact there (I've called it successfully from SoapUI and from a Call Web Service smart service). It seems like there may be an old WSDL cached for this function (the called method was added after the initial version of the WSDL).
The (anonymised) error message coming back from the function is:
The operation [{http://soap.mydomain.com/}getFlatEmployeesForSupervisorSearch] is not present in the binding [{http://soap.mydomain.com/}EmployeeWebServiceServiceSoapBinding].
Available operations in that binding: [
{http://soap.mydomain.com/}getFullEmployeesForSupervisor,
{http://soap.mydomain.com/}getFlatEmployeesForSupervisor,
{http://soap.mydomain.com/}getAllCurrentJobs,
{http://soap.mydomain.com/}getEmployeeStatusDetails,
{http://soap.mydomain.com/}searchDetailEmployee
]
OriginalPostID-148048
OriginalPostID-148048
Discussion posts and replies are publicly visible
Parents
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Great news! This means the WSDL changed and the cache didn't have the latest version yet.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Reply
0
Eduardo Fuentes
Appian Employee
over 9 years ago
Great news! This means the WSDL changed and the cache didn't have the latest version yet.
Cancel
Vote Up
0
Vote Down
Sign in to reply
Verify Answer
Cancel
Children
No Data