Skip to main content

Choose column types, Enums, and images

Column types control the cell editor, validation, binding compatibility, and how Studio interprets a value. Choose a type for what the value means, not only how it looks.

Column types​

  • Text stores names, labels, and rules copy.
  • Number stores values used numerically, such as cost, strength, or quantity.
  • Boolean stores a checked or unchecked state.
  • Color stores a colour for bound fills, strokes, and text.
  • Image stores game artwork or another supported image URL.
  • Enum stores one or more choices from a controlled list and can generate variants.

Change a type from the column header. Studio shows a confirmation when the conversion could change existing values. Review the full column afterwards, especially text converted to numbers or booleans.

The change-column-type confirmation explaining that incompatible values may be converted or cleared

The type controls the cell editor, validation, and which Designer properties can bind to the column. A conversion keeps values that fit the new type and may clear values that do not; ordinary undo is not enough after the dataset saves.

Required values​

Use the asterisk in a column header to mark it as required. Studio will not add a new-row draft until its required values are complete. This setting does not scan existing rows, so review older rows separately and use Export QA for values that are bound into a design.

A required boolean passes only when it is checked. Use required booleans for an affirmative condition, not simply to require that the editor made a true/false choice.

Enums and variants​

A dataset can contain one Enum column with up to 24 named choices. A row can select several choices; Studio treats each selected choice as a separate generated variant of that row.

For example, one Guard row with Standard and Elite selected produces two variants from the same base content. The Designer preview and Export workspace let you inspect those variants.

Use an Enum when variants share the same identity and most content. Use separate rows when each piece needs independently edited rules, artwork, or quantities.

To set up an Enum:

  1. Create an Enum column.
  2. Open Edit enum values in the column header.
  3. Add clear, unique choice names.
  4. Select the relevant choices in each row.
  5. Preview every selected choice in assigned designs.

Renaming or deleting an Enum value updates cells across the dataset and therefore needs the complete row set loaded.

Image cells​

Choose artwork from the game's Assets when possible. Select an image cell (or press Enter on it) and choose Library to pick an image in Choose asset, then confirm with Use asset. Upload adds a new file from your device, and Remove clears the cell. Assets can be previewed, organised, replaced, and traced to their dataset and design usage.

After choosing an image in a row:

  1. Bind an image layer's source to that column.
  2. Preview images with different aspect ratios.
  3. Set the layer's fit, crop, and focal position.
  4. Check image resolution at the intended print size in Export QA.

Before changing structure​

Renaming a column normally preserves its binding key. Deleting a column, replacing the dataset, or changing types can affect every assigned design. Export a TSV, make one structural change, then preview representative rows before continuing.