This guide explains how to use the nested-data settings in JSON to CSV. It is not a separate converter screen. Data.Page uses the same conversion engine, but the choices you make for nested objects and arrays determine whether the CSV is useful in Excel, Google Sheets, or BI tools.
{
"order_id": 1001,
"customer": {
"name": "Alice",
"country": "AU"
},
"items": [
{ "sku": "A-1", "qty": 2 },
{ "sku": "B-7", "qty": 1 }
]
}
Simple child fields can become columns such as customer.name and customer.country. Repeated arrays such as
items usually need a different table shape because one order can contain multiple item rows.
Some data should stay relational. If one customer has many orders and each order has many items, a single flat row can become hard to trust. Separate CSV files for customers, orders, and items are usually cleaner than one very wide spreadsheet.
If the best table shape is not obvious, contact us with a small sample and the report you want to produce.