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
The March 2025 release will initiate the migration process for all accounts to the newer, more accurate parsing behavior. You will have six months to adjust your flows before the migration, and we will provide advance notice. Before switching your account to the new parsing strategy, ensure that any imports generating CSV/XLSX files without mappings do not include unstructured data, and that first-level destination mappings do not reference object or array type fields.
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""}]" |
Comments
Article is closed for comments.