to get a personalized navigation.
to get a personalized navigation.
Hi,
Have you made any changes to the logic regarding updating
shipmentDetailLines recently? We used to be able to update the
lotSerialNumber of an allocation previously, but that is no longer
possible.
We experience this to
have changed sometime between 2023-01-31 10:44:34 and 2023-07-02
14:29:48.
For example, if the shipmentDetailLine looks like this:
{
"shipmentDetailLines": [
{
"lineNumber": 1,
"orderType": "SU",
"orderNbr": "003104",
"inventoryNumber": "ZM000776",
"freeItem": false,
"warehouse": {
"id": "1 ",
"description": "Hovedlager Westcontroll"
},
"location": {
"id": "1",
"name": "Standard"
},
"uom": "STK",
"shippedQty": 1.0,
"orderedQty": 1.0,
"openQty": 0.0,
"lotSerialNbr": "ZPR215126",
"description": "Zaptec Pro",
"allocations": [
{
"lineNbr": 3,
"itemId": "ZM000776",
"location": {
"id": "1",
"name": "Standard"
},
"lotSerialNumber": "ZPR215126",
"quantity": 1.0,
"uom": "STK",
"description": "Zaptec Pro"
}
],
"orderLineNbr": 1
}
]
}
We want to modify the lotSerialNumber. We used to be able to do that using the following data:
{
"shipmentDetailLines": [
{
"operation": "Update",
"lineNumber": {
"value": 1
},
"shippedQty": {
"value": 1.0
},
"allocations": [
{
"operation": "Update",
"lineNbr": {
"value": 3
},
"lotSerialNumber": {
"value": "ZPR215126X"
},
"quantity": {
"value": 1.0
}
}
]
}
]
}
When we send that data now we get the response:
{
"message": "Error: Updating 'Shipment line split' record raised at least one error. Please review the errors.\r\n"
}
Has anything changed recently regarding this?
Best regards
Ronny
Solved! Go to Solution.
I think I found the reason for the error now. The problem was that the lotSerialNumber we tried to update to has been used before.
Using a completely new one fixed the problem.
Would be nice if the error message could include information about the reason for the fail.
Copyright © 2022 Visma.com. All rights reserved.