Question 1

How does the tool pick the records?

Accepted Answer

It walks the tree and finds the deepest element that has two or more children sharing one name. Those repeated elements become the rows — an RSS feed's s, a sitemap's s. Their child elements become the columns (union in first-seen order) and their attributes become @columns. Text-only repeats use the element's own name as the single column.

Question 2

What if my XML has no repeated elements?

Accepted Answer

Then it's a configuration-style document, and the tool renders the flattened view: every text leaf as a Path / Value row (root/settings/debug → true), which is exactly how such files are read. Attributes are skipped in that view — only element text is shown, honestly labelled.

Question 3

Is this the same as the e-invoice XML tool?

Accepted Answer

No — XML Invoice to PDF reads specific invoicing dialects (UBL 2.1, CII) and renders a formatted invoice document with totals and tax blocks. This tool is format-agnostic: any well-formed XML becomes an honest data table. Same parsing engine, completely different output.

XML to PDF

How it works

Frequently asked

How it works

Frequently asked

How does the tool pick the records?

What if my XML has no repeated elements?

Is this the same as the e-invoice XML tool?

Search tools