AlmondTill/G3N API

On this page

updateStyle

mutation · in the family Style

What it does

Edit a style — the top of a product family — change its details.

Edit a Style's mutable attributes. Requires the unrestricted capability + the record's CURRENT revision. A supplied scheme replaces wholesale but is REFUSED once any Product exists; brandId and sizeRunId clear with explicit null; the other lists replace wholesale (empty releases) — every supplied entry re-gated like create.

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.

Arguments

NameTypeRequiredNotes
idID ID!yesThe id of the record.
revisionID ID!yesThe revision id you read on the record; the change is refused if an edit landed in the meantime.
inputEditStyleInput EditStyleInput!yesNo further notes.

Returns

Style Style! — styleType comes from the canned registry (simple | service | kit | bundle — all four realized; kit/bundle variants bear per-variant VariantComponent BOMs since the component slice) and is IMMUTABLE. The scheme is FROZEN once any Product exists. Org availability = the OrgStyle selection; zero dimensions = the corner-store single-cell case.

Example request

mutation ExampleUpdateStyle($id: ID!, $revision: ID!, $input: EditStyleInput!) {
  updateStyle(id: $id, revision: $revision, input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    styleType
    brandId
    sizeRunId
    seasonIds
    tagIds
    code
    taxCategory
  }
}

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": {
    "updateStyle": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "ST-EXMP-0000-000F",
      "type": "Style",
      "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",
      "styleType": "simple",
      "brandId": "01900000-0000-7000-8000-4067736b0000",
      "sizeRunId": "01900000-0000-7000-8000-d314eddc0000",
      "seasonIds": [
        "01900000-0000-7000-8000-92b52b220000"
      ],
      "tagIds": [
        "01900000-0000-7000-8000-decd62770000"
      ],
      "code": "BJ-001",
      "taxCategory": "standard"
    }
  },
  "extensions": {
    "at": {
      "callId": "01EXAMPLE-CALL-ID",
      "version": {
        "requested": {
          "name": "genesis",
          "number": 0
        },
        "serviced": {
          "name": "genesis",
          "number": 0
        }
      }
    }
  }
}

Errors this call can answer

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.