Nested JSON to Excel FAQ

Why does nested JSON show [Record] or [object Object] when imported into Excel?

Excel worksheets only understand two-dimensional rows and columns. Until nested JSON objects are flattened into dot-separated keys (such as customer.address.city) or expanded inside Power Query, child objects cannot map onto flat column cells.

How do I avoid double-counting order totals when expanding nested JSON arrays in Excel?

Wait to sum parent-level totals if you expand child arrays into multiple rows, because parent fields repeat across each child item. Use semicolon-joined array mode when you need one row per parent order, or sum line-item subtotals instead when expanding rows.

How do I stop Excel from deleting leading zeros when opening JSON files?

Power Query automatically samples the first 200 rows and converts numeric-looking strings like "00841" into Whole Numbers. Exporting directly from JSON via a type-aware JSON to XLS converter writes JSON strings as explicit Excel text cells so leading zeros stay intact.

Can I open nested JSON in Excel on macOS without Power Query add-ins?

Yes. Modern macOS Microsoft 365 builds include Get Data (Power Query) for JSON, or you can convert nested JSON directly into a native .xlsx or .xls file in Safari or Chrome on macOS without installing add-ins.