---
title: Updates to the Metafield and Metaobject Definition Formats
date: 2026-11-02
description: Definition exports use an updated format with one column for each validation. Imports still support the older format.
tags: ["Metafield Definitions","Exports","Imports"]
categories: ["Changelog"]
url: https://www.getaltera.com/changelog/2026-11-02-updates-to-metafield-and-metaobject-definition-formats/
---
Metafield and metaobject definition exports use an updated format, with one column for each validation and one row for each metaobject field. Imports still support the older format.

### What's New

- **Validation columns** - each validation has its own column, such as `Validation: Min` and `Validation: Choices` (see [Metafield definition fields](https://support.getaltera.com/en/articles/11490228-metafield-definition-fields#general-id)).
- **One row per field** - metaobject definition exports have one row for each field (see [Metaobject definition fields](https://support.getaltera.com/en/articles/11747962-metaobject-definition-fields#finding-definitions)).
- **Find definitions by name** - metaobject definition imports can find an existing definition by `Name` when `ID` and `Type` are blank.
- **Clear with a blank cell** - in the new format, a blank cell clears values such as `Description`, validations, and `Pinned Position`.

### Improvements

- **Usage counts** - metafield definition exports now show how many metafields use each definition in `Usage Count`.
- **More metaobject details** - exports include the `Updated At` date, Customer Account API access, and web page settings.

### Heads-up

- **New exports** - new definition exports use the new columns, and saved and scheduled exports keep their columns until you edit them.
- **Missing references** - a metaobject definition now fails when it references a type that isn't in the store, and definitions that depend on it fail too (see [MOBD011](https://support.getaltera.com/en/articles/17229125-metafield-and-translation-error-codes#MOBD011)).