Movement Request Header
You can update movement requests after they are in a "Created" status, or update details in custom fields during the life-cycle of a movement request, using the new Movement Request PATCH API.
Movement Request Header URL:
.../wms/lgfapi/v10/entity/movement_request_hdr/id
You can update the following fields using the PATCH method:
Movement Request Detail URL:
.../wms/lgfapi/v10/entity/movement_request_dtl/id
Field | Type |
---|---|
cust_field_1 | String |
cust_field_2 | String |
cust_field_3 | String |
cust_field_4 | String |
cust_field_5 | String |
cust_date_1 | String |
cust_date_2 | String |
cust_date_3 | String |
cust_date_4 | String |
cust_date_5 | String |
cust_decimal_1 | String |
cust_decimal_2 | String |
cust_decimal_3 | String |
cust_decimal_4 | String |
cust_decimal_5 | String |
cust_short_text_1 | String |
cust_short_text_2 | String |
cust_short_text_3 | String |
cust_short_text_4 | String |
cust_short_text_5 | String |
cust_short_text_6 | String |
cust_short_text_7 | String |
cust_short_text_8 | String |
cust_short_text_9 | String |
cust_short_text_10 | String |
cust_short_text_11 | String |
cust_short_text_12 | String |
Sample Patch API Body
"fields": {
"cust_field_1": "Example",
"cust_field_2": "Example",
"cust_field_3": "Example",
"cust_field_4": "Example",
"cust_field_5": "Example",
"cust_date_1": "Example",
"cust_date_2": "Example",
"cust_date_3": "Example",
"cust_date_4": "Example",
"cust_date_5": "Example",
"cust_decimal_1": "Example",
"cust_decimal_2": "Example",
"cust_decimal_3": "Example",
"cust_decimal_4": "Example",
"cust_decimal_5": "Example",
"cust_short_text_1": "Example",
"cust_short_text_2": "Example",
"cust_short_text_3": "Example",
"cust_short_text_4": "Example",
"cust_short_text_5": "Example",
"cust_short_text_6": "Example",
"cust_short_text_7": "Example",
"cust_short_text_8": "Example",
"cust_short_text_9": "Example",
"cust_short_text_10": "Example",
"cust_short_text_11": "Example",
"cust_short_text_12": "Example",
}
}
{