Test with a sample

Before a map goes to work on real documents, test it against a sample. Uploading an example file lets you see exactly what each mapping produces — and lets you catch a mislabelled column or an empty property while it’s still cheap to fix.

Before you start

• You need the Definition Maps update permission to change and test a map. See Roles & permissions.
• Add your field mappings first — see CSV & Excel mapping and PDF extraction.

Preview the mapped fields

1. On the Field Mapping tab, upload a sample file (a CSV, Excel, PDF, XML or JSON that looks like your real documents).
2. DASH analyses the file and shows the fields it detected and the values each mapping pulls out. For XML/JSON sources you’ll see how many fields were detected and how many mapping suggestions are available; use the sample-data view to see the underlying rows.
3. Check each property against the sample values. Fix any mapping that reads the wrong field or comes back empty.

Previewing the values a map pulls from a sample file

Preview mapped test results and validation

To see how your repeating results and validation rules behave together, open the Validation Map tab and use the Mapped Test Results Preview. It runs against your current, unsaved field mappings and shows badges for the rows that pass. Select Refresh preview after any change to re-run it.

The Mapped Test Results Preview with per-row validation badges

Test before you rely on it

Confirm both previews look right before you use the map on real certificates. A mapping that reads the wrong column produces a certificate that fails validation — or, worse, one that passes with the wrong value. Testing here is the fastest place to catch it.

Related

• Create a definition map
• CSV & Excel mapping
• PDF extraction
• Validation rules
• Field transforms & row rules