When mapping fields that contain JSON data to be parsed into a CSV or XLSX file, the default parsing behavior (whether flat or nested) splits values into columns and rows, and drops any parent keys that have nested key/value pairs or arrays. The output only lists the child keys as shown in the middle column of the table below. You can change the parsing behavior to preserve JSON data within a single column to correctly process arrays so that the parsed data is more accurate and reliable. Contact Support to switch your account to the more accurate behavior.
Note
Any connections made after the January 2025 release will operate with the new parsing behavior. Any connections made before the January 2025 release will still continue to use the old parsing behavior.
|
Mapper 2.0 output |
Default CSV output (until March 2025) |
New CSV output |
|---|---|---|
{
"id": "1",
"customer": {
"name": "John",
"age": "30",
"city": "New York"
},
"addresses": [{
"city": "Seattle",
"state": "WA"
}
]}
}
|
id,name,age,city,state 1,John,30,New York,WA Notice that “customer” and “addresses” are absent from the output. |
id,customer,addresses
1,"{""name"":""John"",""age"":30,""city"":""New York""}","[{""city"": ""Seattle"",""state"": ""WA""}]"
|