Large sheets and validation

Large datasets load in pages so the grid stays responsive. A normal page contains up to 500 rows; image-heavy views may use smaller working sets.

Loading more rows

Use Load more to continue through the sheet. If a request fails, keep your existing rows in place and retry after the connection is stable.

Some sheet-wide actions require the complete row window. Studio refuses those actions while rows are still missing rather than silently changing only the visible portion. Load the remaining rows, then try again.

Keep large sheets responsive

• Search or filter before scanning by hand.
• Keep artwork in the Images library instead of pasting large encoded image values into cells.
• Avoid opening the same large dataset in many browser tabs.
• Let imports finish before teammates resume edits.
• Close completed comment threads so unresolved work is easier to find.

Validation

Dataset validation highlights missing required values and values that do not match the column’s expected type. A required boolean must be checked to pass.

Validation is one part of QA. It does not know whether a rules sentence is correct, whether a crop hides important artwork, or whether a long title fits the design.

Use this review order:

1. Resolve dataset validation issues.
2. Preview representative rows and every options variant in the Designer.
3. Open the Export workspace and run generated-design QA.
4. Export a small proof at the intended dimensions.

Changing structure at scale

Before adding, removing, renaming, or changing the type of a widely used column:

• Download a TSV copy.
• Find every assigned design.
• Tell active collaborators.
• Make one structural change at a time.
• Recheck bindings and generated cards before the next change.