AlmondTill/G3N API

On this page

updateOrgVendorItem

mutation · in the family Org vendor item

What it does

Edit a vendor’s catalog entry for one of your variants — their cost, their pack, their SKU — change its details.

Edit a OrgVendorItem'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: Purchasing — Purchase orders, returns to vendors, vendor invoices and supplier records.

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.
inputEditOrgVendorItemInput EditOrgVendorItemInput!yesNo further notes.

Returns

OrgVendorItem OrgVendorItem! — An org vendor item — the (OrgVendor × Variant) JUNCTION: this org buys THIS variant from THIS enabled vendor, carrying the vendor's part number / list cost / MOQ / lead time. Parent = the OrgVendor (the InventoryItem junction stance). The (orgVendor × variant) pair is unique (a live duplicate is CONFLICT/IDENTITY_TAKEN naming the holder; a doomed holder is taken over). OVIs are OPTIONAL by default. Live OVIs block the parent OrgVendor's doom AND the Variant's doom (CONFLICT/REFERENCED); OrgVendor deactivate stays free. Money reuses the MoneyEntry SDL (declared on the Product entry).

Example request

mutation ExampleUpdateOrgVendorItem($id: ID!, $revision: ID!, $input: EditOrgVendorItemInput!) {
  updateOrgVendorItem(id: $id, revision: $revision, input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    variantId
    vendorPartNumber
    moq
    leadTimeDays
    purchasePackId
  }
}

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": {
    "updateOrgVendorItem": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "EI-EXMP-0000-000F",
      "type": "OrgVendorItem",
      "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",
      "variantId": "01900000-0000-7000-8000-8415e73b0000",
      "vendorPartNumber": "<vendor part number>",
      "moq": 1,
      "leadTimeDays": 1,
      "purchasePackId": "01900000-0000-7000-8000-031157c60000"
    }
  },
  "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.