Skip to main content

Columns, options, and images

Choose a type based on how the value behaves, not only how it looks on one card.

Column types​

  • Text holds names, labels, and rules. It can also contain an expression template when a supported field expects one.
  • Number holds values used as numbers, such as cost, strength, or quantity.
  • Boolean is an on/off value. A required boolean is valid when it is checked, not merely present.
  • Colour stores a colour value for bindings and visual choices.
  • Image points to project artwork or another supported image value.
  • Options lets a row select one or more named choices that can generate variants.

Required columns are a dataset-grid validation rule. They help find empty cells before export, but they are not a replacement for reviewing generated cards.

Options and variants​

A dataset can have one options column with up to 24 choices. A row may select more than one choice. Studio treats each selected choice as a virtual generated variant of that row.

For example, one Guard row with Standard and Elite selected can produce two cards from the same base content. The Designer preview and Export workspace let you switch between those variants.

Use options when the variants share most content. Use separate rows when the pieces have independently edited rules, artwork, or identity.

Image values​

Prefer images from the project’s Images library. They are easier to replace, crop, organise, and inspect for usage than temporary external URLs.

After binding an image column:

  1. Preview portrait and landscape artwork.
  2. Check the crop or fit rule.
  3. Confirm the focal point remains inside the frame.
  4. Run QA for low-resolution warnings at the final print size.

Changing a column​

Changing a type can alter existing values. Before a structural edit, check which designs use the dataset and export a TSV copy. After the edit, open those designs and verify their bindings.