mutation UpdateReturn($request: UpdateReturnCommandRequestInput!) {
UpdateReturn(request: $request) {
id
returnNumber
returnDate
customerId
externalNumber
origin
}
}{
"request": {
"returnId": "id"
}
}{
"data": {
"UpdateReturn": {
"id": "id",
"returnNumber": "string",
"returnDate": "value",
"customerId": "id",
"externalNumber": "string",
"origin": "NONE"
}
}
}UpdateReturn
Updates the header data of an existing return - external and internal comment, contact, company, warehouse and sales channel transmission. Line items are updated via the line item endpoint. The state of the return is inferred from its line items and cannot be set directly.
If a request with this mutation’s Idempotency-Key was already completed, the response’s extensions contains an idempotency.{responseName} entry with wasReplayed: true.
UpdateReturn(request: UpdateReturnCommandRequestInput!): Return!Arguments
Returns
Unique ID to identify a return.
The number of the return.
The date when the return was created.
The customer ID.
An arbitrary external reference number for identifying the return.
Indicates the origin of the return, specifying where or how the return was initiated.
The company of the corresponding sales order.
The ID of the sales order if the return has exactly one corresponding sales order.
The ID of the return state.
The ID of the warehouse.
The external comment of the return.
The internal comment of the return.
The contact of the return.
Indicates whether the return should be transmitted to the sales channel.
mutation UpdateReturn($request: UpdateReturnCommandRequestInput!) {
UpdateReturn(request: $request) {
id
returnNumber
returnDate
customerId
externalNumber
origin
}
}{
"request": {
"returnId": "id"
}
}{
"data": {
"UpdateReturn": {
"id": "id",
"returnNumber": "string",
"returnDate": "value",
"customerId": "id",
"externalNumber": "string",
"origin": "NONE"
}
}
}Was this page helpful?