Data mapper in HTTP Actions for multipart endpoints

​@andrewwhitley can you try $STRINGIFY() on your value? Something like this:

• data: $STRINGIFY(<json to mapper syntax>)

Can you also share what you are doing? It’s hard for me to visualize it right now.

​@rgeroulo  - I have tried things like the following as well and am still getting the no data error from the application:
data:
  '$STRINGIFY_JSON({})'

​@Kevin Mok - In my action, my raw json body that is accepted by the application is the following:
data={
<json>
}
The app needs the data key for it to be accepted.
When I try to convert this to the data mapper, even when I have data as the first top most element, the application always says that it is missing the data object. From testing in the logs, it looks like the problem is that the request body needs to be a string that the app is then parsing and the data mapper is mapping it to an object. If there is another Content-Type I can use for this to be accepted as valid form-data of data={<json>}
When looking at how it works in postman/curl the body is included with this syntax:
--form 'data="{}"'

​@andrewwhitley Can you try passing it in the query params section with the Key as data and the Value as the json object?

​@andrewwhitley - I think this would send the whole payload as a string

Can you try something such as this:

EVAL():
    expression: data.$STRINGIFY_JSON()
    args:
        data:
            data:
                xyz: "'test'"