---
title: >-
  metafieldInteger collection condition removed in API version 2027-01 - Shopify
  developer changelog
description: >-
  Shopify’s developer changelog documents all changes to Shopify’s platform.
  Find the latest news and learn about new platform opportunities.
source_url:
  html: >-
    https://shopify.dev/changelog/posts/metafieldinteger-collection-condition-removed-in-api-version-2027-01
  md: >-
    https://shopify.dev/changelog/posts/metafieldinteger-collection-condition-removed-in-api-version-2027-01.md
metadata:
  effectiveApiVersion: 2027-01
  affectedApi:
    - displayName: Admin GraphQL API
      handle: admin-graphql
  primaryTag:
    displayName: API
    handle: api
  secondaryTag:
    displayName: Breaking API Change
    handle: breaking-api-change
  indicatesActionRequired: true
  createdAt: '2026-08-06T13:38:17-04:00'
  postedAt: '2026-10-01T12:00:00-04:00'
  updatedAt: '2026-09-09T11:53:34-04:00'
  effectiveAt: '2026-10-01T12:00:00-04:00'
---

October 1, 2026

# `metafieldInteger` collection condition removed in API version 2027-01

DateOctober 1, 2026

Version[2027-01](https://shopify.dev/changelog?api_version=2027-01)

Flags[Breaking API Change](https://shopify.dev/changelog?filter=breaking-api-change)[Action required](https://shopify.dev/changelog?action_required=true)

SurfacesAPI

Affected APIs[Admin GraphQL API](https://shopify.dev/changelog?api_type=admin-graphql)

As of API version `2027-01`, the `metafieldInteger` collection source condition inputs and types is removed from GraphQL Admin API. If you use `metafieldInteger` to create or read collection source conditions, you need to migrate to `metafieldInt` before you upgrade to API version `2027-01`.

## What changed

With `metafieldInt`, the `value` field on integer metafield conditions changes type from `Int` to `String`, to align with the metafield `value` field on the Storefront API. For details, see the [Storefront `Metafield.value` field reference](https://shopify.dev/docs/api/storefront/latest/objects/Metafield#field-Metafield.fields.value).

The following types and fields are replaced:

* `CollectionSourceInclusionConditionMetafieldInteger` is replaced by [`CollectionSourceInclusionConditionMetafieldInt`](https://shopify.dev/docs/api/admin-graphql/2026-10/objects/CollectionSourceInclusionConditionMetafieldInt)
* `CollectionSourceInclusionConditionMetafieldIntegerRelation` is replaced by [`CollectionSourceInclusionConditionMetafieldIntRelation`](https://shopify.dev/docs/api/admin-graphql/2026-10/enums/CollectionSourceInclusionConditionMetafieldIntRelation)
* `CollectionSourceInclusionConditionInput.metafieldInteger` is replaced by [`CollectionSourceInclusionConditionInput.metafieldInt`](https://shopify.dev/docs/api/admin-graphql/2026-10/input-objects/CollectionSourceInclusionConditionInput#fields-metafieldInt)
* `CollectionSourceInclusionConditionUpdateInput.metafieldInteger` is replaced by [`CollectionSourceInclusionConditionUpdateInput.metafieldInt`](https://shopify.dev/docs/api/admin-graphql/2026-10/input-objects/CollectionSourceInclusionConditionUpdateInput#fields-metafieldInt)

The relation enum members are unchanged (`EQUALS`, `GREATER_THAN`, `LESS_THAN`). The behavioral difference is that `value` is now a `String` instead of an `Int`.

### Writes

These examples show the required switch from `metafieldInteger` to `metafieldInt` and the change in the `value` literal type.

Before:

```
conditionsToCreate: [{
  metafieldInteger: { definitionId: "gid://shopify/MetafieldDefinition/1", relation: GREATER_THAN, value: 2000 }
}]
```

After:

```
conditionsToCreate: [{
  metafieldInt: { definitionId: "gid://shopify/MetafieldDefinition/1", relation: GREATER_THAN, value: "2000" }
}]
```

### Reads

This example shows the updated type condition you need to use when you read collection source conditions.

Before:

```
... on CollectionSourceInclusionConditionMetafieldInteger { relation value }
```

After:

```
... on CollectionSourceInclusionConditionMetafieldInt { relation value }
```

## Action required

Before you move to API version `2027-01`, you need to:

* Update all Admin GraphQL queries and mutations that reference `metafieldInteger` to use `metafieldInt`.
* Ensure all integer metafield condition `value` fields are strings.

If you don’t update your app before you use API version `2027-01`, mutations that send `metafieldInteger` fail validation, and queries that select `CollectionSourceInclusionConditionMetafieldInteger` return errors. You can test `metafieldInt` behavior on `2026-10` before you upgrade to `2027-01`.

`metafieldInteger` continues to work on API versions up to and including `2026-10`. On `2026-10`, integer metafield conditions resolve to `CollectionSourceInclusionConditionMetafieldInt` when present. In API version `2027-01`, `metafieldInteger` is no longer available.

## Related docs

* [Collection source inclusion condition inputs](https://shopify.dev/docs/api/admin-graphql/latest/input-objects/CollectionSourceInclusionConditionInput)
* [Collection source inclusion condition update inputs](https://shopify.dev/docs/api/admin-graphql/latest/input-objects/CollectionSourceInclusionConditionUpdateInput)
* [Collection source inclusion condition metafield `Int` type reference](https://shopify.dev/docs/api/admin-graphql/latest/objects/CollectionSourceInclusionConditionMetafieldInt)
* [GraphQL Admin API reference](https://shopify.dev/docs/api/admin-graphql)