Skip to main content

Columns & Data

The Columns tab in the Template Creator manages all the data columns available for field mapping. Columns can be imported from spreadsheets or added manually.

Importing Data​

Excel Files (.xlsx)​

  1. Click the Import button in the Columns tab.
  2. Select an Excel file from your computer.
  3. Formstamper reads the first row as column headers and displays them in the Columns panel.
  4. All subsequent rows become the data used during stamping.

CSV Files (.csv)​

CSV import works the same way — the first row is treated as headers, and all remaining rows are data.

info

Imported columns are tagged with an Imported badge to distinguish them from manually added columns.

Manually Adding Columns​

You can also create columns directly in the Template Creator:

  1. Click Add Column at the bottom of the Columns panel.
  2. Type a column name.
  3. The column is added with a Manual badge, indicating it was user-defined rather than imported from a file.

Manual columns are useful when:

  • You want to define the data schema before importing a spreadsheet.
  • Your workflow triggers will provide the data dynamically via webhook.
  • You need placeholder columns for testing field mappings.

Column Ordering​

Columns can be reordered via drag and drop. The order affects:

  • The display sequence in the field mapping dropdowns.
  • The visual layout in the data preview table.

Simply click and drag a column card to reposition it.

Column Sources​

Each column displays its origin:

BadgeMeaning
ImportedColumn was imported from an Excel/CSV file
ManualColumn was added manually by the user
MappedColumn is currently mapped to at least one PDF field
UnmappedColumn exists in data but isn't used by any field

Syncing with Field Mappings​

The Columns tab stays in sync with the Field Mapping component:

  • When you map a field to a column in the Field Mapping panel, that column automatically appears in the Columns tab if it doesn't already exist.
  • Deleting a column from the Columns tab will remove it from any field mappings that reference it.
warning

Removing a column that's actively mapped to fields will reset those fields to an unmapped state. You'll need to re-map them.