These are small, made-up files you can use to try the field conversion tool without having to find or type any information of your own. None of them contain anything real about anybody. Each one is a normal web address, so you can open it, save it, or copy what is inside it and paste that straight into the Source box on the tool.
Three ways to use one of these. The quickest is to press the Copy the text button next to a file, then go to the tool and paste it into the Source box. You can also press Open the file to see it in your browser, or save it to your own computer and then use the tool’s own Upload button to load it back in.
You never have to say which kind you have. The tool looks at the first real character. If
it is a < the file is read as XML, and if it is not, the file is read as JSON.
One customer, with a home address nested inside them, a pair of map coordinates nested inside that address, and a list of two orders. It reaches three levels deep on purpose, because that is exactly as deep as Detect Fields From Source looks.
The very same customer as the file above, written as XML instead. This is the useful pair: convert both
with the same field mappings and you can see for yourself that the tool treats them the same way. There is
one honest difference, and it is worth knowing about. XML has no way of writing a plain list without a tag
wrapped around it, so the orders in this file are reached as orders.order, while in the JSON
file the same orders are reached as orders on their own. Every other path in the two files
matches exactly.
A plain list of three orders, with no single record wrapped around the outside of it. Use this one to see
how the tool handles a file that begins as a list: it looks at the first item to work out what the fields
are called, and it tells you it has done that by putting a 0 in the path.
Three books in a catalogue. The same book tag is used once for each of them, which is how a
list is written in XML, so this is the file for checking that a repeated tag really does become a list. Each
book also carries extra pieces of information written inside its own opening tag, such as
id and language, and those become fields whose names begin with an
@ sign.
A small bill. This one is deliberately awkward: each line of it has ordinary words sitting next to other
tags, rather than being one thing or the other. Words in that position are gathered up into a field called
#text, so this is the file to open if you want to see what that means with your own eyes.
Two weather stations, written with prefixes in front of every tag name, such as the wx: in
wx:station. Real XML sent between two companies very often looks like this. The prefix is
dropped when the file is read, so you would write station and not wx:station.
Go to the conversion tool when you have one of these on your clipboard, and paste it into the box marked Source JSON or XML.