Skip to main content
Anchor to MetafieldDefinitionInput

MetafieldDefinitionInput

input_object

The input fields required to create a metafield definition.

•MetafieldAccessInput

The access settings that apply to each of the metafields that belong to the metafield definition.

•MetafieldCapabilityCreateInput

The capabilities of the metafield definition.

•MetafieldDefinitionConstraintsInput

The constraints that determine what resources a metafield definition applies to.

•String

The description for the metafield definition.

•String!non-null

The unique identifier for the metafield definition within its namespace.

Must be 2-64 characters long and only contain alphanumeric, hyphen, and underscore characters.

•String!non-null

The human-readable name for the metafield definition.

•String

The container for a group of metafields that the metafield definition will be associated with. If omitted, the app-reserved namespace will be used.

Must be 3-255 characters long and only contain alphanumeric, hyphen, and underscore characters.

•MetafieldOwnerType!non-null

The resource type that the metafield definition is attached to.

•BooleanDefault:false

Whether to pin the metafield definition.

•String!non-null

The type of data that each of the metafields that belong to the metafield definition will store. Refer to the list of supported types.

•[MetafieldDefinitionValidationInput!]

A list of validation options for the metafields that belong to the metafield definition. For example, for a metafield definition with the type date, you can set a minimum date validation so that each of the metafields that belong to it can only store dates after the specified minimum.

Anchor to useAsCollectionConditionuseAsCollectionCondition
•BooleanDeprecatedDefault:false

Was this section helpful?
OSZAR »