AnsweredAssumed Answered

Call WebService action can't parse XML-schema

Question asked by lehuspohus on Jan 13, 2016
Latest reply on Feb 17, 2016 by philipplucas

Guys, hi!

Recently i discovered a strange behavior of Call Web Service action in my Nintex Workflow 2013.

Problem raised after one of latest updates, but i don't know exactly which one..


Early, our workflow calls web service, usual asmx SOAP webservice which returns an XML response like this:

<?xml version="1.0" encoding="utf-8"?>
<soap:Envelope xmlns:xsi="" xmlns:xsd="" xmlns:soap="">
    <GetPeopleResponse xmlns="">

and i can just select this fields from response in XML browser for save it to variables, like this:


But after one of recent updates this action seems to doesn't work as expected. When i start workflow, it stops with error like:

Failed to invoke web service. 'undefined/undefined:m:GetPeopleResult/undefined:m:Employee/undefined:m:PositionName' has an invalid token

As you see, all xml hierarchy now is 'undefined'.

And when i open action config and choose my fields in XML browser again, now it contains 'undefined' fields too:



I don't know a reason for this behavior, and i can come over this trouble by adding XML Request action, which using XPath builder and correctly getting my fields.

But i don't want to change and republish all my workflows that use Call Web Service action in that way.


So, i want to ask, is it bug of latest updates or feature? If it is a bug, how can i open support ticket?