CSV & Excel mapping

CSV and Excel sources are mapped the same way: you point each definition property at a place in the file. The key choice for each mapping is whether the value is a single fixed field or a repeating one that produces a row of results.

Before you start

• You need the Definition Maps update permission. See Roles & permissions.
• Create the map and upload a sample CSV or Excel file first — see Create a definition map.

Single cell vs each-row

When you map a property, you choose how the source value is read:

• Single Cell — a static value that appears once in the document, such as a batch number or a release date.
• Column (Each Row) — repeating data where each row of the source is one value. Use this for test-results tables, where every row becomes one instance of a repeating entity.

Both a column and a range count as each-row (repeating) data: mapping a whole column, or a range of cells down a column, tells DASH to emit one output record per row rather than a single value.

Screenshot pendingChoosing Single Cell or Column (Each Row) when mapping a property

Map repeating test results

Repeating results are mapped under a repeating entity so each row becomes one instance:

1. On the Field Mapping tab, find the Repeating Entity Mappings section.
2. Turn on Enable Each Row Mode for the entity (it reads Each Row Mode: ON once enabled). This tells DASH to create one output element per source row.
3. Map each value property in the entity to its Column (Each Row) source field. Columns that vary per row appear under Variable Columns (per row); values that are the same on every row appear under Static Columns (same all rows).

In the certificate document view, results are grouped by entity and shown as a table — the property names become the columns and each source row becomes a row of the table.

Static values inside a repeating table

A value that is the same on every row (for example a shared method or unit) can still live inside a repeating entity — map it from a Static Columns (same all rows) field so it is filled in for every instance.

Mapping the same results across more than one table

Some documents carry several test-result tables that all feed the same repeating properties. Map the property once, then add each table as an additional source range for that same property. When you generate the output:

• the XML output merges the rows from every table into one repeating group; while
• the PDF and the certificate review screen keep each source table as a separate section, so the on-screen layout matches the original document.

Mapping a column once lights it up in every table that shares the same header, so you don’t have to repeat the work per table.

Related

• Create a definition map
• Field transforms & row rules
• Validation rules
• Test with a sample
• PDF extraction