What XML is
XML marks up data with nested named tags and optional attributes. It is verbose, strict about being well-formed, and can carry a schema that says what shape a document must have.
Enterprise integrations, government data feeds, RSS, SOAP services and older document formats.
What Qlik is
A Qlik load script block using LOAD INLINE, which embeds the data in the script itself.
QlikView and Qlik Sense developers.
What changes when you convert XML to Qlik
The first repeating element is treated as the rows. Attributes are read alongside child elements and prefixed so they do not collide with a same-named tag. Nesting one level deep becomes dotted column names; deeper structures are kept as text.
Suitable for small reference tables. For anything large, load from a file instead.
What carries over from XML to Qlik
XML records 2 things about a table that Qlik has no way to hold.
Qlik wants a type for each column, and XML does not record one, so each column is typed from what its values look like. A column of digits that should stay text - a zip code, a phone number, a leading-zero id - is the usual thing to check afterwards.
XML can hold a value that is itself a list or an object. Qlik has only flat cells, so nested values are flattened into one cell rather than being spread across columns.
A line break inside a cell ends the row in Qlik, so line breaks are replaced rather than carried through.
Qlik marks header cells differently from data cells, so the keys are lifted out and written once as a marked header row rather than repeated on every row.
The identifier 007 comes out of the Qlik as 007. Reading it as a number would have made it 7, and an id that changes value is worse than one that stays text.
The role "Analyst, data" survives with its comma, in one cell rather than split across two. That is the first thing to check in any converted table, and the usual place a Qlik file goes wrong.
The quotes around Jonah "Jo" Pryce are left as a plain quote character in the Qlik.