I used the Web Request action in Nintex 2013 to get all lists from a web. I stored the result in a variable. The variable only contains a GUID, no XML string to work with.
Executing the request in the action works fine, returning a valid XML string.
Any idea, why the result of the web requests does not contain the XML string?
Are you using syntax something like this?
This works for me, but let me know if you're still stuck?
Hi Vadim, hi Jan,
first of all thanks for your replies. Attached I send a bit more information about the issue.
I am using the 'Web Request' action in combination with "Get", not "SOAP". I am using a simple REST call ('Website-URL/_api/web/lists') and save the result in a variable. The value of the variable is something like a GUID, not an XML string.
Because of this I clicked the green execute button. I then clicked the green execute button again. I get the correct result with status 200 and a XML string (just like a REST call via the browser).
But clicking the "Test connection" button I get the message "Status: FORBIDDEN". The call failed. Any idea about the reason of this message? May be this is why the result value of the REST call is a GUID and not a XML string.
I know that this is older than heck, but I recently ran into this same problem.
I was able to resolve it using some terrible XSLT.
In this case, my Web Request is just querying all the list items (Using standard REST request '/_api/lists/gettitleby('sharePointListTitle')/items?$select=ID), and returning the properties.
Transform the XML using a Query XML action, and copy the following XSLT code:
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="text() | comment() | processing-instruction()">
This should completely remove all of the attributes (completely) leaving only the main tags and values.
Now you are free to use XPaths as normal!
If you wanna see what your response XML actually is (after you've transformed it), you can do so by sending yourself an email with your response variable wrapped in the fn-XmlEncode() function.
(because I'm terrible at XSLT - This thread got me almost there: Working with XML in Nintex Workflows (simplified) )