Review a launch checklist
2 added lines, 1 removed line and 4 matched lines. The status edit is a removal plus an addition.
Use the default tool settings.
A starting point you can verify.
Small fictional datasets, explicit settings and expected outputs. Open a prepared case or download the files to run it yourself.
All files are created for these tutorials. They contain no real customer records and may be reused in your own work.
Reconcile two inventory exports
With sku as the key: 1 changed row, 1 added row, 1 removed row and 1 unchanged row.
Match by sku; comma delimiter; exact cell text.
Inspect an order without changing its IDs
The postal code stays "00123", paid stays true, and the order remains a JSON object.
Use the default tool settings.
Keep postal codes and multiline notes
2 records. Postal codes stay strings; a comma and a line break stay inside their notes cells.
Use the default tool settings.
Check YAML values and their JSON types
yes stays a string, true becomes a boolean, and null remains distinct from empty text.
Direction: YAML to JSON.
Review an order-status update
3 differences: status changed, note removed and tracking added. Moving object keys adds no changes.
Use the default tool settings.
Clean a four-record contact export
4 data rows become 2 after trimming, blank-row removal and exact deduplication.
Use the default tool settings.
Turn a contact list into three unique lines
5 input lines become 3. First-seen order and the uppercase SALES address are preserved.
Use the default tool settings.
Use a sample as an acceptance check
Start with unchanged inputs and settings. Compare your result with the supplied output, then change one field or option at a time. A successful example shows how this tool behaves; it does not validate your own application’s business rules.