createContactAssignment

mutation · in the family Contact assignment

What it does

Create a new contact’s assignment to a record — who is the buyer on this vendor, the manager at this store at your organization.

Create a ContactAssignment — one role-tagged contact attachment; requires the unrestricted capability.

Who may call it

Capability area: Purchasing — Purchase orders, returns to vendors, vendor invoices and supplier records.

• Owner
• Manager
• Associate Manager
• An API key whose scope allows api:createContactAssignment

Arguments

Returns

ContactAssignment ContactAssignment! — A contact assignment — ONE role-tagged attachment of a Contact to a HOST construct (org group / organization / logical facility / vendor / corporate customer). Parent = the HOST (the CollectionMember stance — hostId rides the header parentId). The (contact, host, role) triple is unique (a live duplicate is CONFLICT/IDENTITY_TAKEN naming the holder); REMOVE = doom (TWO_STATE — history preserved); re-assigning mints a NEW record via marker takeover. Role↔host applicability is registry DATA. At most 48 live assignments per host.

Example request

mutation ExampleCreateContactAssignment($input: NewContactAssignmentInput!) {
  createContactAssignment(input: $input) {
    id
    sysId
    type
    caption
    status
    parentId
    rootId
    createdAt
    updatedAt
    revisionNum
    revision
    contactId
    hostType
    role
  }
}

Variables:

{
  "input": {
    "caption": "Blue jeans",
    "hostId": "01900000-0000-7000-8000-5c71ac820000",
    "hostType": "organization_group",
    "contactId": "01900000-0000-7000-8000-4db757ce0000",
    "role": "<role>"
  }
}

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

Example response

{
  "data": {
    "createContactAssignment": {
      "id": "01900000-0000-7000-8000-37386ae00000",
      "sysId": "CA-EXMP-0000-000F",
      "type": "ContactAssignment",
      "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",
      "contactId": "01900000-0000-7000-8000-4db757ce0000",
      "hostType": "organization_group",
      "role": "<role>"
    }
  },
  "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.

Used in

• Keep contacts for suppliers, customers and sites