Has this problem been resolved, or do your customers still experience IPPExceptions? ... View more

In the next release (version 10.20) this problem is solved. Let us know if the situation still occurs. ... View more

Hi Erik, I can confirm the issue. This has been escalated as a bug and will be reviewed. 1) Create a KIT Item with multiple Warehouse (Warehouse Details: 1-Default, 2 Optional)  2) POST KIT Assembly with that KIT Item specifying the non-default warehouse in the payload. { "type": "P", "hold": { "value": false }, "date": { "value": "2024-01-17" }, "itemId": { "value": "KIT01" }, "revision": { "value": "1" }, "description": { "value": "string" }, "warehouse": { "value": "2" }, "location": { "value": "1" }, "quantity": { "value": 1 } } Output: 3) Check "Inventory Transaction History", it'll show the movement based on warehouse "1" even though we've specified Warehouse"2"   4) Create KIT Assembly manually in the ERP UI with Warehouse "2" 5)  Check "Inventory Transaction History" again. Now, it shows the movement correctly, Warehouse "2" ... View more

Hi, There are occasionally some issue related to the cache not being updated, however there is no documentation regarding this and it is not always a problem.  ... View more