> For the complete documentation index, see [llms.txt](https://knowledgebase.fabricdata.com/studio/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://knowledgebase.fabricdata.com/studio/features-and-functionality/bulk-upload-via-csv.md).

# Bulk Upload via CSV

Create new Records and update existing ones in bulk, using a CSV file.

Bulk Upload lets you add or change many Records at once instead of one at a time. A single file can create new Records, update existing ones, or both, including whole Series hierarchies.

#### Before you start

| You want to              | You need                                                            |
| ------------------------ | ------------------------------------------------------------------- |
| Use Bulk Upload          | **Bulk Actions: Write**                                             |
| Create Records           | **Studio Library: Create**                                          |
| Update Records           | **Studio Library: Update**, for those Records, Sections and locales |
| Export Records to update | **Data Delivery** access                                            |

Bulk Actions permissions don't override your Record permissions. If you upload a row you don't have permission for, that row fails and the rest of the file is still processed.

<figure><img src="https://2273874994-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FpbuQPZAuVlwuAEzIi462%2Fuploads%2Feg9B439pYCEvg0Z6ESPS%2Fimage.png?alt=media&amp;token=b28d2089-2086-4ac9-9e8e-9cf84d5c1292" alt=""><figcaption></figcaption></figure>

#### Create Records in bulk

1. In the Studio Library, select **Bulk Upload**.
2. Download the **create template**. It includes example rows and a README with completion guidance.
3. Add a row for each new Record.
4. Upload the file by dragging and dropping it, or by browsing for it.

**Link Records in the same file**

Give each row a temporary `row_id`. To place a Record under another Record in the same file, put the parent's `row_id` in the `parent_id` column. To place it under a Record that already exists in Origin Studio, use `parent_studio_id` instead.

Example: a new Series with one Season and two Episodes.

| row\_id   | primaryTitle   | workType | parent\_id | sequenceNumber | locale | releaseYear |
| --------- | -------------- | -------- | ---------- | -------------- | ------ | ----------- |
| s1        | The Lighthouse | Series   |            |                | en     | 2026        |
| s1-se1    | Season 1       | Season   | s1         | 1              | en     | 2026        |
| s1-se1-e1 | Pilot          | Episode  | s1-se1     | 1              | en     |             |
| s1-se1-e2 | The Keeper     | Episode  | s1-se1     | 2              | en     |             |

#### Update Records in bulk

Use one of two approaches:

**Export, edit and re-upload (recommended)**

1. In the Studio Library (List View), select the Records to update.
2. Select **Export** in the selection bar. You can export up to 50,000 Records at once.
3. When the export finishes, download the CSV from **Data Delivery** or **Background Jobs**. It's already filled in with the Records' current values.
4. Edit the values you want to change. Keep the `studio_id` column so each row matches its Record.
5. Upload the file with **Bulk Upload**.

**Start from the update template**

Download the **update template** from **Bulk Upload**, add a row for each Record using its `studio_id`, and upload it.

#### How rows are processed

| Row has                        | Result                       |
| ------------------------------ | ---------------------------- |
| A `studio_id`                  | Updates that existing Record |
| No `studio_id`, but a `row_id` | Creates a new Record         |

#### Columns

| Column             | Required                     | Notes                                                                 |
| ------------------ | ---------------------------- | --------------------------------------------------------------------- |
| `row_id`           | For creates                  | A temporary ID you assign                                             |
| `studio_id`        | For updates                  | The existing Record's Studio ID                                       |
| `primaryTitle`     | Yes                          |                                                                       |
| `workType`         | Yes                          | Movie, MovieEdit, Series, Season, Episode, EpisodeEdit or Compilation |
| `parent_id`        | No                           | The `row_id` of a parent in the same file                             |
| `parent_studio_id` | No                           | The Studio ID of an existing parent Record                            |
| `sequenceNumber`   | Season, Episode, EpisodeEdit | Position within the parent                                            |
| `locale`           | Yes                          | The language of the values in the row, such as `en`                   |

Other columns use each field's **field key** as the header. The templates are generated from your tenant's own fields, so they always match your setup.

* Separate multiple values in one cell with `|`, for example `Drama|Mystery`.
* Values for fields that use a dataset must exactly match a value in that dataset.
* To add values in another language, use one row per language with the matching `locale`. \[Confirm]

#### Limits

* CSV files only.
* Up to 50,000 rows per file.
* Files are scanned for safety before processing. Unsafe files are rejected.

#### Track progress and fix errors

Uploads run as Background Jobs, so you can keep working. When the job finishes, open its **report** to see which rows succeeded and which failed, and why.

Problems with individual rows don't stop the upload. Common reasons a row fails:

* A required value is missing, or `workType` or `locale` is invalid.
* `studio_id` doesn't match an existing Record.
* A parent can't be found, or the change would break the hierarchy.
* A value isn't in the field's dataset, or the wrong multi-value separator was used.
* You don't have permission to create or update that Record or field.

Correct the failed rows and upload them again. You don't need to re-upload rows that succeeded.
