updateCharacteristic

mutation · in the family Characteristic

What it does

Edit a product characteristic — a typed attribute products carry (material, care, age rating) — change its details.

Edit a Characteristic's mutable attributes. Requires the unrestricted capability + the record's CURRENT revision.

Careful

Edits take effect immediately and write a new revision; the old revision stays in history.

Who may call it

Capability area: Catalog editing — Changing what you sell — the details of styles, products, variants and their identifiers.

Owner
Manager
Associate Manager
An API key whose scope allows api:updateCharacteristic

Arguments

Name	Type	Required	Notes
`id`	ID `ID!`	yes	The id of the record.
`revision`	ID `ID!`	yes	The revision id you read on the record; the change is refused if an edit landed in the meantime.
`input`	EditCharacteristicInput `EditCharacteristicInput!`	yes	No further notes.

Returns

Characteristic Characteristic! — A characteristic — a master-list entry for VALIDATED product values (serial-number, warranty period, …): value type + validation grammar + optional unit; distinct from Tags (unstructured labels), Categories (navigation), and Options (variant-driving). Canned + custom: system-shipped IMMUTABLE templates are copied via copyCannedCharacteristic; group-defined customs are created directly — references (the Manufacturer format map; the spine) always point at group-owned constructs, never templates. TWO_STATE — no inactive (a master-list entry is usable or gone).

Example request

mutation ExampleUpdateCharacteristic($id: ID!, $revision: ID!, $input: EditCharacteristicInput!) {
  updateCharacteristic(id: $id, revision: $revision, input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    valueType
    unit
    code
  }
}

Variables:

{
  "id": "01900000-0000-7000-8000-37386ae00000",
  "revision": "01900000-0000-7000-8000-b7960e180000",
  "input": {
    "caption": "Blue jeans"
  }
}

Send it with the envelope naming the version: "extensions": {"at": {"version": {"name":"genesis","number":0}}}.

Example response

{
  "data": {
    "updateCharacteristic": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "CH-EXMP-0000-000F",
      "type": "Characteristic",
      "caption": "Blue jeans",
      "status": "active",
      "parentId": "01900000-0000-7000-8000-065235280000",
      "rootId": "01900000-0000-7000-8000-a093dd800000",
      "createdAt": "2027-01-31T00:00:00.000Z",
      "updatedAt": "2027-01-31T00:00:00.000Z",
      "revisionNum": 1,
      "revision": "01900000-0000-7000-8000-b7960e180000",
      "valueType": "string",
      "unit": "<unit>",
      "code": "BJ-001"
    }
  },
  "extensions": {
    "at": {
      "callId": "01EXAMPLE-CALL-ID",
      "version": {
        "requested": {
          "name": "genesis",
          "number": 0
        },
        "serviced": {
          "name": "genesis",
          "number": 0
        }
      }
    }
  }
}

Errors this call can answer

VALIDATION/INVALID — Something in the request is not valid. (VALIDATION)
AUTHN/REQUIRED — Sign in to do this. (AUTHN)
AUTHZ/FORBIDDEN — Your role does not allow this action. (AUTHZ)
RATE_LIMIT/THROTTLED — Too many requests in a short time. (RATE_LIMIT)
NOT_FOUND/* — That record could not be found. (NOT_FOUND)
CONFLICT/* — The record’s state, or a change made in the meantime, does not allow this; the codes are on the CONFLICT page. (CONFLICT)
VALIDATION/VERSION_REQUIRED — The request did not say which app version it came from. (VALIDATION)

Dry run

Add dryRun: true to the request envelope (extensions.at) to rehearse this call: every check runs, the write is rehearsed against the current records and nothing is stored; the answer is the refusal a real call would give, or the record it would create. Every response to a rehearsal carries dryRun: true, so a rehearsed record is never mistaken for a saved one.