to get a personalized navigation.
to get a personalized navigation.
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"
}
]
}
Yesterday we had this error again, so still seemingly random from our side. Has this been looked into?
Thanks
PUT: https://integration.visma.net/API/controller/api/v1/kitassembly/P/560021
{"description":{"value":"REPLACED TEXT, , uppr\u00E4knat antal: 1818,00"},"location":{"value":"9"}}
Response: 400 Bad Request
Headers: {
Date: Thu, 11 Apr 2024 19:20:55 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: f2c0f48c-f923-46b0-857b-a6fae8b5be19
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=Wed, 10-Apr-2024 19:20:54 GMT; HttpOnly
Connection: close
Transfer-Encoding: chunked
Content-Type: application/json; charset=utf-8
Expires: -1
}
{"message":"Error: 'tstamp' cannot be empty."}
Hi Marcus!
We have created a ticket for this for our development team, but unfortunately they have not been able to prioritize this case as of now.
- Suzdar
Hi Marcus!
Does this problem occur everyday? How long has it happened?
- Suzdar
Hi,
No, it does not occur everyday. These kinds of requests are done a few times a month and they are mostly working.
This error was first noticed back in January and now it happened again yesterday, tried again today with the same request and got the same error.
Thanks.
Copyright © 2022 Visma.com. All rights reserved.