[POST] .../v1/techmapoperation/moveoperations
Moves an operation from one document to another Use this workflow method to move selected technological map operation rows from one tech map document to another. The request body must contain doc_from_id, doc_to_id and a non-empty ids array; source and destination documents must be different, the selected operations must all belong to the source document and both documents must be in the editable state expected by the persistent checks. The source document must be locked, the destination document must not be locked before the move, both documents must be unposted and the persistent layer locks the destination document as part of the operation. The current request user must have tech map operation move permission; missing body, invalid ids, same source and destination, denied access, document state conflicts, membership mismatches, no affected rows or storage failures are returned as HTTP 200 ErrorResult business errors.
Request Parameters
| Name | Type | Required | Description |
|---|---|---|---|
| doc_from_id | Int64 | Required | Source document ID. |
| doc_to_id | Int64 | Required | Destination document ID. |
| ids | Array of Int64 | Required | Operation IDs to move from the source document to the destination document. |
Request Example
{
"doc_from_id": 7301,
"doc_to_id": 7302,
"ids": [
8301
]
}Response Parameters
| Name | Type | Description |
|---|---|---|
| ok | Boolean | Indicates whether the request completed successfully. |
| result | Update | Update operation result. |
Response Example
{
"ok": true,
"result": {
"row_affected": 1,
"ids": [
8301
]
}
}