Reorder Metadata within Product Type

PUT 
/product/:guid/metaData/reorder

Change the order of Metadata within the Product Type by specifying a new predecessor successor pair. The predecessor will be removed from its current place in the Product Type and reinserted directly before (visually: above) the successor. The successor will retain its current place in the Product Type.

Note it takes two operations to reorder a Metadata to the last position: first reorder it before the last one, then reorder the last one before it.

Request

Path Parameters

guid uuidrequired

The guid of the Product Type.

application/json

Body

Input data

predecessor uuid

The guid of the Metadata that will be moved within the Product Type.

successor uuid

The guid of the Metadata that determines where to move the predecessor.

Responses

204

Reordering of MetaData within Product Type successful.

403

Unauthorized. You do not have permission to modify the Product Type.

application/json

Schema

Schema

error_code string

The general error code.

error_description stringrequired

The exact reason of failure.

Example (from schema)

{
  "error_code": "string",
  "error_description": "string"
}

404

Product Type or Metadata not found.

application/json

Schema

Schema

error_code string

The general error code.

error_description stringrequired

The exact reason of failure.

Example (from schema)

{
  "error_code": "string",
  "error_description": "string"
}

406

Request is invalid, see error context for validation errors. Or, predecessor and successor are equal.

application/json

Schema

Schema

error_code string

The general error code.

error_description stringrequired

The exact reason of failure.

Example (from schema)

{
  "error_code": "string",
  "error_description": "string"
}

500

Internal server error. Reordering failed or successor does not exist.

application/json

Schema

Schema

error_code string

The general error code.

error_description stringrequired

The exact reason of failure.

Example (from schema)

{
  "error_code": "string",
  "error_description": "string"
}

Loading...