Exporting results

The replacement table for any run is the record of exactly what changed. You can take it out of Piixie as CSV whenever you need it outside the app.

From the history entry

Open a completed run in the history tab. The replacement table there has:

• Download CSV — saves a .csv file of every entry: type, original, replacement (and the generator for synthetic values).
• Copy all as CSV — copies the same data to the clipboard, ready to paste into a spreadsheet.

A typical export looks like:

type,original,replacement,generator
NAME,Marcos Patel,David Romero Gil,faker:person.fullName
ID,1029384,84913366,faker:string.numeric
DOB,14/03/1982,02/11/1979,faker:date.birthdate
EMAIL,[email protected],[email protected],faker:internet.email
NAME,Dra. Ruiz,Dra. Lucía Sáez Marín,faker:person.fullName

What it’s good for

• Audit and compliance. A reviewable record of every value that was changed, attached to the document it came from. Pair it with the profile snapshot the run stored.
• A second pair of eyes. Hand the CSV to a colleague to sanity-check the mappings without giving them the app.
• Seeding a dictionary. The original→replacement pairs are exactly what a dictionary holds. (Piixie can also promote them directly — see build a dictionary from a run.)

A privacy note

The export contains original PII values in the first column — that’s what makes it useful, and what makes it sensitive. A results CSV deserves the same care as the source document: store it somewhere controlled, and delete it when you’re done. The same caution applies to Piixie’s local database, which holds these values for history and search.

Searching before you export

The history table has its own search (matching originals and replacements). Filtering doesn’t change the export — Download CSV and Copy all as CSV give you the full table — so export everything, then filter in your spreadsheet if you need a subset.

Next

• History
• Build a dictionary from a run
• Privacy & data storage