This page details the data displayed in the Property Editor for a Data Source.
These properties contain all editable settings that define how the Data Source behaves and how it connects to Layouts.
Name #
The title you assign to this Data Source for easy identification within your project.
Not to be confused with “File Name”.
ID Column #
The column used as a unique identifier for each row. Must contain unique values.
- The values in the selected column will be what are used as references for Data Linking to Layer properties.
This input field will open a drop-down containing each of the column names in your connected spreadsheet.
Name Column #
The column whose values are shown in the Row Selection panel (A) and in the Set Editor.
This input field will open a drop-down containing each of the column names in your connected spreadsheet.
Variants Column #
The Variants Column defines which Variants apply to each row in your Data Source. For each variant a row supports, a different card will be generated.
While any column can be assigned for this purpose, it’s best practice to use a dedicated column specifically for managing variant information.
Each cell (row) in this column can contain the text:
- “Standard”:
- Meaning the row does not use any variants.
- One or more variant names:
- Separated by commas (
,), indicating all the variants that this card supports.
- Separated by commas (
Example:
A row with the valueFoil, AlternateArt, Promo
would indicate that this card supports all three of those variants.
The Variants Column is primarily used for Data Linking. It is not available for Layout Mapping, as variant behavior is handled separately.
For full details about how variants work and how they affect output generation, see the Variants page.
Default Front Layout & Default Back Layout #
Each Data Source can specify:
- A Default Front Layout
- A Default Back Layout
These Layouts define how each row of data will appear when rendered as a card. Data Sources that assign Layouts to these fields will have their columns selectable for Data Linking in their Layer properties.
When combined with Data Linking, properties within the Layout automatically pull data from the corresponding cells in the Data Source.
Front Layouts are always included in Print and Export operations by default.
Back Layouts, however, are only generated when the “Export Backs” option is explicitly checked in the Print or Export dialogs. If unchecked, only the Front Layouts will be produced for each card.
The preview of this Layout will be displayed in the Layout Preview panel of the Data Source Editor.
Front Layout Map & Back Layout Map #

In addition to assigning default Layouts, each Data Source can define Front and Back Layout Maps.
These allow you to use different Layouts for specific rows based on the value of a chosen column in your data table.
How It Works
A Layout Map dynamically selects which Layout is used for each card by matching column values in your Data Source.
- The drop-down labeled “Column” lists every column available in your data sheet.
- You can select any column to use as the key for layout mapping. The only exception is the automatically generated “<Variant> column, which is only used for Data Linking from Layers.
- Once a column is selected, the table below it lists all unique values from that column in the “Column Value” section.
- You can then assign a specific Layout to each of those values in the “Layout” section.
Example
If you have a column named “Type”, and it contains the values Creature, Spell, and Artifact, you can map each to a different Layout:
| Column Value | Layout |
|---|---|
| Creature | CreatureLayout |
| Spell | SpellLayout |
| Artifact | ArtifactLayout |
When exporting or printing, each card will automatically use the Layout assigned to its “Type” value.
Count Column #
Determines how many copies or instances are generated for each row.
This input field will open a drop-down containing each of the column names in your connected spreadsheet.
Default Export Profile #
Defines how data from this source is exported (for example, as images, print files, etc.).
This input field will open a drop-down containing the file names of every Export Profile in the current project.
- This Export Profile will be automatically set when you initiate an Export operation on this Data Source.
Google Sheet ID #
Read-only (can’t be edited) field that displays the unique ID of the Google Sheet used to populate the Data Source.
- This field is only visible for Data Sources populated from a Google Sheet. It will not be visible when pulling from a different type of spreadsheet.
- NOTE: If a Google Sheet was incorrectly linked during creation, deleting the Data Source and re-creating it is the best option to fix the issue.
Localization Map #

The Localization Map connects the languages defined in your Project Properties to specific sheets within your spreadsheet-based Data Source.
This allows you to maintain multiple translations or language variants of your data in one file while ensuring the correct version is used when generating output. As a result, you don’t have to maintain separate Data Sources for each translation.
How It Works
Each entry in the Localization Map links a “Language” to a “Sheet” within your spreadsheet.
- Language:
- This dropdown lists all languages defined in your Project Properties.
- Sheet:
- This dropdown lists all the available sheet tabs from your connected spreadsheet (Excel or Google Sheet).
When output operations (like Export or Print) are run, the selected output language determines which sheet is used for that Data Source.
This ensures that every generated card uses the correct localized data set.
Example:
If your project includes English, French, and Japanese as languages, and your spreadsheet contains separate tabs namedSheet_English,Sheet_French, andSheet_Japanese, you can map each language to its corresponding sheet.When exporting in French, only the data from
Sheet_Frenchwill be used.