AlmondTill/G3N API

On this page

updateTransferRequest

mutation · in the family Transfer request

What it does

Edit a stock-transfer request between your locations — change its details.

Edit a TransferRequest'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: Inventory operations — Receiving, counting, transferring and moving stock.

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.
inputEditTransferRequestInput EditTransferRequestInput!yesNo further notes.

Returns

TransferRequest TransferRequest! — A stock transfer request: a requesting LF asks variants x quantities of the group (open sourcing) or of ONE targeted source LF. Lines are EMBEDDED, VARIANT-keyed + birth-fixed (max 24 — TR-o); cancelled is the ONE doomed terminal (lists filter it); fulfilled/closed_short are IMMUTABLE non-doomed history — a write there refuses CONFLICT/IMMUTABLE.

Example request

mutation ExampleUpdateTransferRequest($id: ID!, $revision: ID!, $input: EditTransferRequestInput!) {
  updateTransferRequest(id: $id, revision: $revision, input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    requestingOrganizationId
    targetLogicalFacilityId
    neededBy
    priority
  }
}

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": {
    "updateTransferRequest": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "TR-EXMP-0000-000F",
      "type": "TransferRequest",
      "caption": "Blue jeans",
      "status": "draft",
      "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",
      "requestingOrganizationId": "01900000-0000-7000-8000-93bd40d40000",
      "targetLogicalFacilityId": "01900000-0000-7000-8000-2938ce830000",
      "neededBy": "<needed by>",
      "priority": "low"
    }
  },
  "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.