Source data, target data and logs

The Document screen shows Supply Lens's tidy version of a transaction. When something does not add up, you need to go deeper: what exactly arrived, what exactly was sent, and what Supply Lens recorded along the way. In this lesson you will learn to read source and target data and use logs, the two tools that turn "I think" into "I know".

Source data: what actually arrived

From a Document, open the links menu and choose its source data. This is the original data exactly as the sending system sent it. Look here when you need to know whether a problem started upstream.

On the source data screen you can:

• download the data to your device, or copy it to your clipboard
• open its logs
• reprocess, complete or cancel it (covered in Module 3)
• use the links menu to go to the Documents created from it

Target data: what actually went out

From a Document's links menu, open the target data created from it. Each record shows which Integration it was for, with its logo, name and key, so if a Document went to several places you can tell them apart. The source data screen and the target data screen work the same way.

Reading raw data

Raw data opens in a viewer with syntax highlighting, built-in search, collapsible sections and a minimap. It recognises many formats, including JSON, XML, CSV, EDIFACT, TRADACOMS and X12.

• Format expands minified (squashed-up) JSON, XML or EDI so it is easier to read, without changing the data.
• Versions. If a record has more than one stored file, pick an earlier version from the list to see it.
• Compare. Select two records on a list and choose Compare to see them side by side. You can also compare two versions of the same file. An option sorts JSON keys on both sides so the same data in a different order does not show as changed.

Logs: what Supply Lens recorded

Every Document, source data and target data record has logs: messages written while it was being built, converted or sent. Click Logs to open them in a window over the page, so you keep your place. For a Complete Document, logs are mostly informational. For a Failed one, they contain the message that explains why.

Getting the most out of logs:

• Filter by severity so warnings and errors stand out. When an item has failed, its logs open showing only errors.
• Open an error to read its full details in a dialog. Anyone who can view a log can do this.
• See who did what. Entries made by a person show a person icon; hover to see their name. Automatic entries show no icon.
• Logs for many items at once. Select up to 100 rows on the Documents, source data or target data list and click Logs above the list.
• Download CSV saves all entries at the severities you have ticked as a spreadsheet, up to 10,000 entries. Useful when sending details to Support.