Skip to main content

Large datasets and validation

Studio loads large datasets in windows to keep the grid responsive. A normal window can contain up to 500 rows; datasets with image columns may use a smaller window because each image requires more work.

A partially loaded dataset showing 80 of 96 rows loaded and the Load more rows action

Load the complete sheet​

Scroll near the end to load the next window automatically, or choose Load more rows in the status bar. The status shows how many rows are currently available.

Search works on the rows currently loaded, so load the complete dataset before treating its results as sheet-wide. Studio blocks actions that must update the whole sheet instead of silently applying them to one window. These include replace, import, adding or duplicating rows, row reordering, column type changes, column deletion, and Enum renames or deletion.

If an action reports that it needs the complete dataset:

  1. Choose Load more rows until the status disappears.
  2. Retry the action.
  3. Review the result before making another structural change.

Dataset export can fetch remaining rows itself, but it still produces the complete sheet rather than only the current window.

Keep a large grid easy to use​

A long grid of game cards with one highlighted row, a magnifying glass, and a meeple marking the result
  • Use search operators instead of scanning manually.
  • Store artwork in the Assets library rather than encoded image data.
  • Make one structural change at a time.
  • Use row colours and cell comments for review status.
  • Close or approve finished comments so has:open-comments stays useful.

Validate required content​

Required columns control whether Studio can add a new-row draft. Empty text, number, colour, image, or Enum values fail that check; a required Boolean must be checked. Existing rows are not highlighted or scanned solely because a column is required.

Use this review order:

  1. Clear any search so all rows are visible.
  2. Review required columns for gaps, especially in older or imported rows.
  3. Search for open comments and finish the decisions.
  4. Preview difficult rows and every Enum variant in the Designer.
  5. Run Export QA for unresolved bindings, overflow, image resolution, and print risks.
  6. Export a small proof at the intended size.

The required setting cannot judge rules wording, crop composition, or whether a title fits. Dataset review and rendered-output review are both necessary.