Hi,   We are doing these kind of requests on a regular basis and seemingly random we are getting this error on a few requests every once in a while.  Ive seen this problem posted several times on the forum but for other entities and its often been resolved with a patch/software update for Visma.NET so maybe this is a similar problem.   Request/response: PUT: https://integration.visma.net/API/controller/api/v1/kitassembly/P/560019 {"description":{"value":"REPLACED TEXT, Grey, uppr\u00E4knat antal: 855,00"},"location":{"value":"9"}} Response: 400 Bad Request Headers: { Date: Wed, 20 Mar 2024 20:07:12 GMT Server: Apache/2.4.52 Server: (Debian) Server: OpenSSL/1.1.1n Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 0a757de1-8b0c-4dd9-ac41-bc7d3ce2da05 X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_REAL_0046 Access-Control-Expose-Headers: Request-Context Cache-Control: no-cache X-XSS-Protection: 1;mode=block Request-Context: appId=cid-v1:745938e4-e9a9-4ad4-b9ae-c57b6b9a0cc9 Set-Cookie: <crumbs>; path=/; expires=Tue, 19-Mar-2024 20:07:12 GMT; HttpOnly Connection: close Transfer-Encoding: chunked Content-Type: application/json; charset=utf-8 Expires: -1 } {"message":"Error: 'tstamp' cannot be empty."}   Data for the Kitassembly thats being updated (Some texts have been anonymized) { "type": "P", "refNo": "560019", "status": "B", "hold": false, "date": "2024-03-04T00:00:00", "postPeriod": "202403", "itemID": "150435 ", "revision": "1", "description": "REPLACED TEXT, Grey", "warehouse": "1 ", "location": "1 ", "uoM": "ST", "quantity": 855, "createdDateTime": "2024-03-04T08:43:18.677", "lastModifiedDateTime": "2024-03-04T08:43:18.677", "stockComponentLines": [ { "lineNbr": 3, "itemId": "IN150435 ", "description": "REPLACED TEXT, Grå, 90x75cm", "location": "7 ", "uoM": "ST", "quantity": 855, "unitCost": 25.398994, "componentQty": 1, "minComponentQty": 0, "allowComponentQtyVariance": false, "maxComponentQty": 0, "allowComponentSubstitution": false, "disassemblyCoeff": 1, "allocations": [ { "lineNbr": 4, "location": { "id": "7", "name": "VAS förädling Janus" }, "lotSerialNumber": "", "quantity": 855, "uom": "ST" } ] } ], "nonStockComponentLines": [ { "lineNbr": 5, "itemId": "Arbete ", "description": "Arbete VAS (lägg till information)", "uoM": "ST", "quantity": 855, "unitCost": 0, "componentQty": 1, "allowComponentQtyVariance": false, "minComponentQty": 0, "maxComponentQty": 0 }, { "lineNbr": 6, "itemId": "Frakt ", "description": "Frakt VAS (lägg till information)", "uoM": "ST", "quantity": 855, "unitCost": 0, "componentQty": 1, "allowComponentQtyVariance": false, "minComponentQty": 0, "maxComponentQty": 0 }, { "lineNbr": 7, "itemId": "Etikett ", "description": "Etikett VAS arbete (lägg till information)", "uoM": "ST", "quantity": 855, "unitCost": 0, "componentQty": 1, "allowComponentQtyVariance": false, "minComponentQty": 0, "maxComponentQty": 0 } ], "kitAllocations": [ { "lineNbr": 8, "location": { "id": "1", "name": "Standard" }, "lotSerialNumber": "", "quantity": 855, "uom": "ST" } ] }   ... View more

Im creating a purchase receipt via the API. I then want to add purchase order lines. This works some of the time and some of the times I get an error that ExpirationDate is missing.    So instead of just population the Lines property with the lines I want from the purchase order I also populate the allocation property with the required data. Then i start to get errors that some lines contain unassigned location and/or lot/serial number. Im not sure what that means, but im posting correct values in the request.   The main issue as I see it is the first ExpirationDate missing error, not sure why that is thrown, and only in some cases. I have not figured out when its thrown and when its not.   Side note: If i manually add the same lines in the initial post request that create the purchase receipt, it works fine.    The first request with only lines:   POST: https://integration.visma.net/API/controller/api/v1/PurchaseReceipt/2500577/action/addpurchaseorderlines Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Id: |mC569LrL59w=.887f20fa_4. Content-Type: application/json; charset=utf-8 Content-Length: 73 } {"purchaseOrderLines":[{"orderNbr":"2300132","lines":[{"lineNbr":"1"}]}]} Response: 400 Bad Request Headers: { Date: Tue, 19 Sep 2023 14:51:13 GMT Server: Nginx Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 9aab4b0a-dc05-4587-9e4a-dc1c3ffc9041 X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_DEMO_0017 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Mon, 18-Sep-2023 14:51:10 GMT; HttpOnly Connection: close Transfer-Encoding: chunked Content-Type: application/json; charset=utf-8 Expires: -1 } {"message":"Error adding purchase orders to receipt: Error: Inserting 'Purchase receipt line split' record raised at least one error. Please review the errors.\r\nError: 'Expiration date' cannot be empty.\r\n"}     The second request with lines and allocations.    POST: https://integration.visma.net/API/controller/api/v1/PurchaseReceipt/2500589/action/addpurchaseorderlines Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Id: |CAUmqwPHhLw=.cf51796f_5. Content-Type: application/json; charset=utf-8 Content-Length: 292 } {"purchaseOrderLines":[{"orderNbr":"2300132","lines":[{"lineNbr":"1"}],"allocations":[{"operation":"Insert","lineNbr":{"value":1},"location":{"value":"1"},"lotSerialNumber":{"value":"000000"},"quantity":{"value":500.00},"expirationDate":{"value":"2026-09-19T08:23:55.5486531+02:00"}}]}]} Response: 500 Internal Server Error Headers: { Date: Wed, 20 Sep 2023 06:24:00 GMT Server: Nginx Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: 171c594a-3636-41d0-9cef-19b86d0a4925 X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_DEMO_0017 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Tue, 19-Sep-2023 06:23:58 GMT; HttpOnly Connection: close Transfer-Encoding: chunked Content-Type: application/json; charset=utf-8 Expires: -1 } {"message":"VismaId: 171c594a-3636-41d0-9cef-19b86d0a4925. Error adding purchase orders to receipt: Sales order error: One or more lines contain unassigned location and/or lot/serial number."}     ... View more