I have done something similar to create(not read XML) because the xml example I was trying to replicate had a structure that CR and Excel doesn't like(nested XSD).
There was no table type schema available and just one record had 250 columns,250 rows when analysed in Excel, making it hard to tell what was needed.
So,
I opened the xml as a text file and pasted the header text into a text box in the CR report header, and details into the detail section.
Each element or attribute is on its own row to ease editing but each section in CR is just one textbox
I replaced the variable parts (attributes/elements)from my source Access Query or Excel Table.
I have group headers/footers that are conditionally suppressed and all sorts of other fancy CR options on formula fields and sections.
It helps if you create formula fields with same name as the element/attribute name so
CR text within your text box:
<AddressLine1>{@10:OrganisationDetails-Name}</AddressLine1>
<CityOrSuburb>{@15:Address-CityOrSuburb}</CityOrSuburb>
<Location>{@16:Address-Location}</Location>
Output XML:
<AddressLine1>MAERSK LINE</AddressLine1>
<CityOrSuburb>LIVERPOOL</CityOrSuburb>
<Location>GBLIV</Location>
Even if the variable data is a direct field from your DB table, use a formula with a number in the name so you get things in the correct order and can see reused fields
In effect, my CR is a mail merge.
It is possible to output text as xml if you export as txt(NOT XML) and set rows per page to 0, save extension as filename.xml, even though the file extn will show as .txt in the save as window.
My XML works a treat, and I have loaded a million records this way when our IT programmers couldn't do this for me as there were too many variants in the source data(hence conditionaly supressed footers)
I had never used xml before, but I managed to figure it out OK.
Doesn't help READING in the xml though, I had same issue, only helps creating XML.