Nested XML to CSV: structured tables vs one-table flattening
Both approaches produce CSV data, but they handle repeated and nested XML very differently.
Why the conversion approach matters
XML can represent parents, children, and repeating groups. A one-table converter puts those values into a single wide CSV. That can be convenient for simple XML, but nested records may require duplicated parent values or become difficult to relate reliably.
Tidelose detects table-like structures, exports them as separate CSV files, and adds _row_id and
_parent_row_id columns where needed so related rows can be joined again.
Feature comparison
| Feature | Tidelose converter | Typical one-table converter |
|---|---|---|
| Nested XML | Creates separate CSV files for detected tables and links parent and child rows with generated IDs. | Combines nested values into one table, often repeating parent data. |
| Review before export | Shows detected tables, row counts, columns, types, and relationships before conversion. | Produces the flattened output without a structural preview. |
| Output control | Lets you review and rename each generated CSV file. | Uses an automatically selected output name. |
| Download | Packages all related CSV files together in one ZIP archive. | Produces a single flattened CSV file. |
A simple nested XML example
An order can contain several items. Flattening normally repeats the order fields for every item. A structured conversion can keep orders and items in separate CSV files and link each item to its order.
orders
├─ order 1001
│ ├─ item BK-101
│ └─ item NT-204
└─ order 1002
└─ item PN-310Which approach should you choose?
A single flattened CSV is often sufficient when the XML is already simple and table-shaped. Preserving related tables is more useful when your XML contains repeating child records or when you need to retain parent-child relationships for later analysis or import.