Streamlining Asset Pipelines with Shotgrid Custom Fields & Automation

Problem: Metadata Fragmentation in Large Studios

In many animation houses, asset information lives in spreadsheets, emails, and disparate tools. When a 3‑D model is updated, the new version number may be recorded in a Google Sheet, an email thread, or a local file, while the Shotgrid record still shows the old number. This decentralization leads to versioning errors, lost context, and a tedious manual audit process.

Thesis: Keep Everything in Shotgrid with Custom Fields and Automation

Shotgrid’s Custom Fields let you add arbitrary metadata directly to an entity (Asset, Shot, Task). The Automation Engine can react to field changes, enforce workflow rules, and create downstream actions. Together they centralize data, reduce human error, and give teams a single source of truth.

1. Creating a Custom Field

Below is a step‑by‑step guide to add a dropdown called 3D Model Version to Asset records.

1. Navigate to Settings → Custom Fields (requires Admin or Settings role).
2. Click New Custom Field.
   • Entity: Asset
   • Name: 3D Model Version
   • Type: Dropdown
   • Options: v1.0, v1.1, v1.2, Approved
   • Default: v1.0
   • Validation: Enforce that only the listed options can be selected.
3. Click Save and verify the field appears in the Asset editor.

Verification: Open any Asset, confirm the new dropdown exists, and that it accepts only the defined options.

2. Building an Automation Rule

We’ll create an automation that triggers when 3D Model Version is set to Approved. The rule will: 1) change the Asset status to In Production and 2) create a QA Task.

1. Navigate to Automation → New Automation.
   • Trigger: Field Change – Asset – 3D Model Version.
   • Condition: New value equals Approved.
2. Add the first action: Update Status → Set status to In Production.
3. Add the second action: Create Task.
   • Title: QA Review – {Asset.Name}
   • Assignee: QA Team Lead
   • Due Date: +3 days from trigger
   • Parent: The Asset record
4. Save and enable the automation.

Verification: In a sandbox project, change the dropdown to Approved on a test Asset. The status should switch to In Production and a new QA Task should appear in the Activity feed.

3. Trade‑offs & Limitations

• UI Clutter: Too many custom fields can overwhelm users. Keep the UI clean by grouping fields in tabs or hiding rarely‑used ones.
• Database Load: Each field change triggers a write. If you automate on every change, you may see performance hits. Limit automations to critical fields or batch updates.
• Permissions: Users without the proper role can delete or modify custom fields, breaking the pipeline. Use role‑based access to safeguard field definitions.
• Data Duplication: If a field duplicates existing metadata (e.g., storing a version number that already exists in the Asset name), confusion can arise. Align custom fields with your studio’s data dictionary.

4. Actionable Next Steps

1. Create a sandbox project to experiment with custom fields and automations.
2. Identify the core metadata needed for your pipeline (e.g., version, review status, asset type).
3. Define a field lifecycle: when to create, update, or retire a field.
4. Write a simple automation script (see example above) and test it in the sandbox.
5. Gather team feedback on field placement and automation triggers.
6. Iterate: adjust field options, add validation, refine automations.
7. Once validated, promote changes to the production environment and update documentation.

By embedding metadata in Shotgrid and automating status transitions, studios can reduce manual checks, ensure consistent versioning, and accelerate the handoff between artists and QA.