Skip to content
Novus Examples
xml2 KB

Fieldnote Supply Shop: Returns and RMA register XML

Returns and RMA register XML for Fieldnote Supply Shop. The same 4 authorisations as returns-rma.csv as XML. The root element ReturnAuthorisations declares count="4" and contains exactly that many ReturnAuthorisation children, each with 11 child elements.

xml

application/xml

2 KB
Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Rows
4

Binary xml: no in-browser preview. Download it above to open in a compatible application.

Specifications

Document Set
ecommerce
Industry
retail
Source Kit
retail-commerce
Synthetic
true
As Of
2026-09-08
Rows
4
Root Element
ReturnAuthorisations
Encoding
UTF-8

Testing contract

Expected to pass
Scenario
Parse the XML and assert the declared count against the parsed element count.
Expected result
The document is well formed, the root count attribute is 4 and exactly 4 ReturnAuthorisation elements are present, each carrying a unique number attribute.

What is a .xml file?

XML (Extensible Markup Language) is a verbose, self-describing markup language using nested tags, attributes, and namespaces to represent structured, hierarchical data. It supports schemas, entities, and validation and underlies many document and data formats. It remains common in enterprise, publishing, and interchange contexts.

How to use this file

Use an example XML file to test parsers, namespace and schema validation, XPath queries, and protection against entity-expansion and external-entity attacks.

How to use this file for testing

“Fieldnote Supply Shop: Returns and RMA register XML” is a deterministic Novus Examples fixture for Data import. Realistic faker-generated datasets with documented schemas for testing import and ETL flows.

Documented properties for this file: 4 rows · UTF-8. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such, expect parsers to fail loudly rather than silently accept them.

Data fixtures document their exact quirks (delimiters, encodings, null handling, schema, and row counts) in the spec table. Point your parser or importer at the file and assert it handles the documented edge cases; clean and deliberately-messy siblings make before/after diffs straightforward.

Code examples

import xml.etree.ElementTree as ET

tree = ET.parse("returns-rma.xml")
root = tree.getroot()
print(root.tag, [c.tag for c in root][:5])

Generated by generation/industry_documents.py. Free for any use, no attribution required, license.