Skip to main content
Data & Schema

Not translated yet — showing English.

Working with Game Data

Data is where your schema gets its records. Every entity has a table of records here that you can browse, filter, create, edit, import and export. Open it from Data under Engineering in the sidebar; it shows the environment selected in the top bar. The structure of the records comes from your schema.


The Data view

The sidebar lists your Entities with their record counts, and any Views you've saved; Search tables… narrows the list. Select an entity to see its records.

ControlWhat it does
SearchFinds records of the selected entity.
FilterNarrows the list by field values.
ColumnsChooses which fields are shown.
Save viewSaves the current entity, filters and columns as a view in the sidebar, for queries you keep running.
Import · ExportLoad records from a file, or save them to one. See below.
New recordCreates a record.

Select records with the checkboxes to export or delete them together.


Create a record

Click New record, or Create first record on an empty entity. The form follows the entity's fields:

Field kindIn the form
PrimitiveAn input for its type, with the default filled in.
Enum referenceA list of the enum's values.
RelationshipThe ID of the record to link to.
InclusionNot in the form: fill it in from the record's panel after it is created.

Fields marked required must be filled in. Click Create to save the record.


Edit a record

Click a record to open its panel.

TabWhat it shows
ValuesThe record's fields, and a card for every part it includes. Edit on a card edits that card's fields.
Referenced byThe records of other entities that link to this one.
HistoryNot filled in yet: the rows shown are placeholders.
JSONThe whole record as JSON.

Delete at the bottom of the panel deletes the record. A record's ⋯ menu in the list also offers Edit record, Duplicate and Delete.

A singleton entity has a single record, so it opens as one form instead of a list.

Edit all makes every field editable at once, with a card for each included part; Save all or Cancel all finishes the edit.


Import records

Choose the file

Select the entity, click Import, choose CSV or JSONL and drop the file in. A CSV file needs a header row. The file is read right away, and the dialog moves on to mapping.

Map the columns

Columns are matched to fields by name. Check the matches, change any that are wrong, and look over the preview of the first rows. The footer counts valid and skipped rows and mapped columns.

Import

Click Import with the number of rows. When it finishes, the dialog reports how many rows were imported and how many were skipped in the mapping check. Rows go to PlayServ one at a time: if the platform refuses one, the dialog stays on Importing…. Close it and check the list for the rows that made it.

Some fields can't be imported

The record ID and included parts are left out of an import. Fill in the parts afterwards, in each record's panel.


Export records

Export saves records of the selected entity as a JSON file; with records selected, it saves just those.

Export covers the records loaded so far

The file holds the records the list has loaded, not necessarily the whole entity; the notification says how many of the total it saved. Page through the list first if you need more of them.


Next steps

Last updated on 16 Oct 2026