Skip to main content

Import a spreadsheet into a dataset

Studio imports CSV, TSV, TXT, and XLSX files. It can also read a Google Sheet that is shared as Anyone with the link can view.

Import replaces the dataset

Import removes every current row and column and creates replacements from the spreadsheet. Existing design bindings may break because the new columns have new keys. Export a TSV first and check the target dataset name before confirming.

Prepare the spreadsheet​

  1. Put column names in the first row.
  2. Use one row per game piece.
  3. Keep each column to one kind of value.
  4. Remove title blocks, merged cells, subtotals, and decorative blank columns.
  5. Finalise column names before import.

Studio detects useful column types from imported values. Review every detected type afterwards, especially numbers with leading zeroes, booleans, colours, and Enum-like text.

The spreadsheet import window with file and Google Sheets sources and a warning that the dataset will be replaced
  • Upload file accepts CSV, TSV, TXT, and XLSX. XLSX uses the first worksheet.
  • Google Sheets accepts a sheet shared as Anyone with the link can view. Remove public sharing afterwards if it is no longer needed.
  • The parsed filename, row count, and column count describe the replacement. Replace dataset remains unavailable until parsing succeeds.

For XLSX files, Studio reads the first worksheet. CSV, TSV, and TXT imports detect their delimiter from the content. Type detection checks the imported values in a fixed order, so mixed columns are safest as text until you have reviewed them.

Import a file​

  1. Open the dataset that will be replaced.
  2. Choose Import → Upload file.
  3. Select the spreadsheet and review the detected row and column count.
  4. Choose Replace dataset.
  5. Review column types and required settings.
  6. Open each assigned design and repair any unresolved bindings.

Import needs the complete current dataset loaded before it can replace it. If Load more rows is shown, load the remaining rows first.

To start a new dataset from a spreadsheet instead of replacing one, choose New dataset, add the file or Google Sheets link under Import spreadsheet, then choose Create dataset.

Import Google Sheets​

  1. In Google Sheets, set general access to Anyone with the link can view.
  2. Choose Import → Google Sheets in Studio.
  3. Paste the sharing link and choose Import from Google Sheets.
  4. Review the detected size, then replace the dataset.
  5. Remove public sharing afterwards if it is no longer needed.

Studio imports the tab shown in the link, or the first tab when the link does not name one. To import a different tab, copy the link from the browser address bar while that tab is open. Anyone with the link can read that sheet while sharing is enabled. Do not use this route for confidential content that must not be public.

Google Sheets imports are limited to 5 MiB. Local spreadsheet files are parsed in the browser, so a very large file also needs enough memory on the device doing the import.

Export a dataset​

Choose Export to download a tab-separated .tsv file. The header contains each column's stable binding key, which can differ from its displayed name after a rename. Image values are resolved to usable URLs.

If every row is loaded, the export includes the current grid. If rows remain unloaded, save pending changes first; Studio then fetches the complete dataset in 500-row windows. It stops rather than producing a partial file if the dataset changes during that fetch or a later window cannot be loaded.

A dataset export contains spreadsheet data only. It does not include rendered game pieces, comments, designs, game fonts, all source artwork, or a complete game backup. Use the Export workspace for generated pieces and game archive tools for a whole-game copy.

Verify a round trip​

After import, check:

  • Punctuation and quotes. Tabs and line breaks inside cells are flattened in a TSV export.
  • Numbers that need leading zeroes.
  • Boolean and colour values.
  • Every Enum selection.
  • Image cells and bound image layers.
  • Representative generated pieces and Export QA.