Extract Variable JSON payload introducing escape character for "/"

[sarfernando]

Hi,

We have a back end response that contains "/" and we use the Extract Variable policy to extract the node that contains this character inside. The EV policy introduces an escape character to the "/" so the response has data looking like "xxxxx \/ xxx" when we want it to be "xxx / xxx". I would have thought forward slashes are not escaped? How can this be avoided?

Thanks.

.........................................................................

[dknezic]

Do you have an example of how your policy is currently configured?

[sarfernando]

EV.ExtractResponseData data

<ExtractVariables name="EV.ExtractResponseData">
    <DisplayName>EV.ExtractResponseData</DisplayName>
    <JSONPayload>
        <Variable name="data" type="object">
            <JSONPath>data</JSONPath>
        </Variable>
    </JSONPayload>
</ExtractVariables>

[sarfernando]

The AM policy is :

<?xml version="1.0" encoding="UTF-8" standalone="yes"?>
<AssignMessage async="false" continueOnError="false" enabled="true" name="AM.SetRetailersResponse">
    <DisplayName>AM.SetRetailersResponse</DisplayName>
    <Properties/>
    <Set>
        <Payload contentType="application/json">
            { "data": {data}, "links": { "self": "{selfLink}" } }
        </Payload>
    </Set>
    <AssignTo createNew="false" transport="http" type="response"/>
</AssignMessage>

[itravindrasingh]

Hi @sarah fernando, can you please provide the request payload sample for debugging perspective?

[sarfernando]

The request is something like:

{"data":{"test":[
{"id":"1010","name":"1st Ene Pty Ltd"},
{"id":"2034","name":"Click Ene / Am Ene"}]}

[sarfernando]

And we see the response after EV policy as :

{"data":{"test":[
{"id":"1010","name":"1st Ene Pty Ltd"},
{"id":"2034","name":"Click Ene \/ Am Ene"}]}

[itravindrasingh]

ev-demo-rev2-2019-07-26.zip

I am not getting the error now, here is the sample proxy I have attached.

[dknezic]

The extract variable is adding the \ as you mentioned.

Try a javascript implementation instead to do the same thing (Get the data field from a json response, and assign to data variable) such as follows

	var response = context.getVariable('response.content')
	var responseJson = JSON.parse(response)
	context.setVariable('data', JSON.stringify(responseJson.data))

[dchiesa1]

This is true, and also, the backslash is benign. See my answer.

[dchiesa1]

I see that the problem you described - unnecessary backslash-escape of a forward slash - seems to have gone away?

Just wanted to point out that in JSON, the backslash escape of a forward slash should be benign. Nothing to worrry about. It should be handled by the JSON processor transparently.

ref: https://stackoverflow.com/a/1580664/48082