JSON Payload values in a JSON payload builder step

[PJ 3000]

I have an action that creates a payload using 5 payload builder steps

The last step, number 6 uses the payload generated in step 2 as the value on one of the name pairs.

The output looks fine, until tested, where it shows that the value of that payload contains a slot of escape /" in the payload.  Which is clearly not what i want.

STEP 6 PAYLOAD

STEP 2 PAYLOAD

Is there a way without using JSON Parser as the client doesn't have the integration hub standard license just starter and without scripting the whole REST again.  Is there a way to just format that payload so it doesn't have the slashes in the payload.

[Richard Hine]

PJ,

Personally I wont touch the payload builder for creating JSON. Its much more robust and reliable to create it manually in a script step.

If you nest your JSON like you have it will double escape your characters like you are seeing. I would avoid using the payload builder and use script steps like this:-

output:

You will find it is all treated as strings and you can more easily plug them together.

Will need you to rework your action but it will save you a lot of heartburn.

Hope this helps,

Richard

[PJ 3000]

hey, it works, great.  When i plug it into the step builder to put all the steps together it escapes the output again.

as soon as you put the output from any other step in to a payload builder step to build it, it escapes the charachters. It is so frustrsating

[Richard Hine]

PJ,

And that is the main reason I've completely stopped using payload builder.

If you generate your strings using script steps, you can then assemble the whole thing using one final script step....

You can also do what I often do which is hand the record off to a script include do the whole lot and return the built payload.

Richard

[PJ 3000 · Accepted solution]

Hi

you are a hundred percent spot on with the fact payload builder needs work, the whole flow integrations does it, having useful step plugins and not being licensed is ridiculous.

Finally managed to find an amalgamation of the 2 and went for output the payload in a builder step and managing to then parse that output as a strign: