# Save where a file type's results go on a board

Replaces the result mappings of one file type on one board, for one file-column scope: {documentType, definitionId, fileColumnId (null = any file on the record; a file column narrows the set to files held in it), mappings: [{field, target: same_row|linked_row, relationColumnId, destinationColumnId, updateRule: fill_empty|review|overwrite, createMissingLink}]}. The board's other scopes are left as they are; the answer is the board's whole set. Every column must be on the board (or, for linked_row, on the board the relation column points at) and able to hold a value — not a relation, person, file or computed column; one field per destination column. createMissingLink makes and links a record on the related board when the relation links nothing. [] clears the scope. Unknown keys are refused. Admin only.

Access class: `workspace:admin`.

## Endpoint

`PUT /v1/workspace/processor/result-mappings`

## Request body

Content type: `application/json`.

```json
{
  "definitionId": "",
  "documentType": "string",
  "fileColumnId": "",
  "mappings": [
    "string"
  ]
}
```

## Responses

### 200

the action's answer

Content type: `application/json`.

```json
{
  "data": [
    {
      "createMissingLink": true,
      "definitionId": "",
      "definitionKey": "string",
      "destinationColumnId": "",
      "destinationKind": "string",
      "documentType": "string",
      "field": "string",
      "fileColumnId": "",
      "id": "",
      "problem": "string",
      "relationColumnId": "",
      "status": "string",
      "target": "string",
      "updateRule": "string",
      "updatedAt": "2026-01-01T00:00:00Z"
    }
  ]
}
```

### default

a refusal: `{"error": "<what a person needs to read>"}`. 401 no credential, 402 the plan does not include this, 403 the seat does not, 404 the thing does not exist or is not yours to see.

Content type: `application/json`.

```json
{
  "error": "string"
}
```
