Update dimension value

Outcome

Change one dimension value code or display name. Posted journal tags remain immutable.

Before you start

• Verify the intended environment, authenticated identity and specifically approved organization context.
• The published application permission is settings:write. Discover the exact granted canonical Books workspace and bind it separately from action input.
• Approve the actual mutation, accounting inputs and any provider/recipient effects before CLI --confirm or MCP confirm:true. Fixture identifiers and simulated provider responses authorize no live operation.

Discover the target

topolo whoami --json
topolo actions get app_topolo_books.dimensions.values.update --detail --json
topolo resources topolo-books --json
topolo workspaces list topolo-books --json

• Set BOOKS_WORKSPACE_ID to the exact granted workspace returned by discovery.
• dimensionId: Resolve this exact identifier through the related published reads for the same organization and workspace; never infer it from a name.
• valueId: Resolve this exact identifier through the related published reads for the same organization and workspace; never infer it from a name.

Request

PATCH /api/dimensions/{dimensionId}/values/{valueId}

Inspect and test this action. Save the reviewed input as payload.json; supply credential/resource context separately.

Input fields

Inspect nested fields and the complete input schema.

Effects

• Changes one dimension value code or display name. Existing journal tags remain immutable.

Interpret the response

Read $.value.id for the returned dimension_value identifier. Empty collections and nullable fields do not discover a target.

Call app_topolo_books.dimensions.list with includeArchived true and compare the value fields.

Inspect the success schema. CLI/MCP add their own transport envelope; CLI --detail requests the full result.

Worked examples

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.

Run a reviewed request

Save the input from the selected worked example as payload.json. Validate and inspect the plan before calling the action; refused examples demonstrate errors and are not instructions to execute.

CLI:

topolo actions validate app_topolo_books.dimensions.values.update --data @payload.json --json
topolo actions plan app_topolo_books.dimensions.values.update --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --json
topolo actions call app_topolo_books.dimensions.values.update --resource-type workspace --resource-id "$BOOKS_WORKSPACE_ID" --data @payload.json --confirm --detail --json

MCP tool and arguments for the first successful example:

{
  "tool": "topolo_call_action",
  "arguments": {
    "actionId": "app_topolo_books.dimensions.values.update",
    "input": {
      "dimensionId": "dim_456ddc9670304180a235d531a75f9e69",
      "valueId": "dimv_a2eaf135d804488197305559cda19f89",
      "name": "London office"
    },
    "resourceType": "workspace",
    "resourceId": "<exact granted workspace id>",
    "confirm": true,
    "detail": true
  }
}

Successful response · HTTP 200

Input · payload.json:

{
  "dimensionId": "dim_456ddc9670304180a235d531a75f9e69",
  "valueId": "dimv_a2eaf135d804488197305559cda19f89",
  "name": "London office"
}

Captured response · HTTP 200

{
  "value": {
    "id": "dimv_a2eaf135d804488197305559cda19f89",
    "dimension_id": "dim_456ddc9670304180a235d531a75f9e69",
    "code": "LON",
    "name": "London office",
    "status": "active",
    "created_at": "2026-10-05T19:42:58.239Z",
    "updated_at": "2026-10-05T19:42:58.246Z"
  }
}

HTTP 200. Call app_topolo_books.dimensions.list with includeArchived true and compare the value fields.

Refused response · auth_error

Input · payload.json:

{
  "dimensionId": "dim_7f3c1b",
  "valueId": "dimv_9a12c4",
  "name": "Commercial"
}

Captured response · HTTP 401

{
  "error": "API key validation failed"
}

HTTP 401. SDK error code auth_error. Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

Verify the result

• Call app_topolo_books.dimensions.list with includeArchived true and compare the value fields.

Errors and recovery

• auth_error (HTTP 401): Authenticate in the intended organization again. Verify whoami and the exact Books application/workspace binding before retrying; do not switch identity to work around a refusal.

These are observed local refusals. Shared authentication, schema validation and resource authorization can also refuse before the route. Preserve the actual error, details and request id.

Recovery boundary

Read dimensions.list before changing it, then send the previous code and name back.

Related actions

• List tracking dimensions: List active tracking dimensions and their selectable values, or include archived records for settings and historic journal display.

Evidence

Actual Books route handlers and the exported Worker were exercised against five local SQLite D1 concern databases with all committed migrations, the real posting Durable Object and local R2. Route captures use synthetic verified Auth; Worker captures use synthetic Auth transports. Nexus, Brand, Notify, Pay, Mercury and Xero responses are explicitly simulated at the provider transport boundary. Captures prove local request/response behavior and canonical SDK projection, not live bank access, payment movement, email delivery, provider eligibility, tax compliance, encrypted custody, scheduled execution, deployment or production completion. Fixture identities, credentials, addresses and records authorize no live operation.