User Profile
MarcusHedlund
9
Posts
0
Kudos
0
Solutions
10-01-2025
14:59
Hi, Thanks for your answer. We have acutally implemented something close to what you describe and has not had any missed entities since then, so hopefully that will take care of the problem. Its not the cleanest solution, but it works. We can leave it at that and if we should experience further issues with this I will reach out again. Thanks
... View more
12-12-2024
15:48
Hi, We are experiencing a problem with data missing if its created to close to the time of the fetch request. As an example, We fetch Supplier invoices on a regular basis and we use the lastModifiedDateTime filter to only fetch new invoices since last time we checked. Sometimes we are not getting all of the invoices that are created since last fetch. Every time this has happened and we looked into this we noticed that the entities that are not fetched has a lastModifiedDateTime that is very near to the time of the request. Within 30 seconds every time. A supplier invoice with "lastModifiedDateTime": "2024-12-09T07:59:45.327" was not fetched when doing the following request was done at "2024-12-09T08:00:05.244" 'https://integration.visma.net/API/controller/api/v1/supplierInvoice?lastModifiedDateTime=2024-12-09T07%3A30%3A00.000' Other invoices with earlier lastModifiedDateTime was fetched in the same request. This has happened on other endpoints/entities as well, for example JournalTransactions. Is it to be expected that there could be differences between what lastModifiedDateTime says and whats actually fetched in a request when these two events happens close to each other? I hope my explaination is understandable, if not im available to answer any questions. Thanks
... View more
12-04-2024
08:12
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."}
... View more
21-03-2024
13:02
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.
... View more
21-03-2024
09:20
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
21-09-2023
13:09
Hi, That seems to be exactly whats happening, that also explains why some orders works and some dont. Thank you.
... View more
20-09-2023
14:10
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
18-09-2023
15:45
Hi, Thank you. Yes, I have tried that. I get a 204 response but the transfer number field is not updated/populated on the inventory receipt, so no luck there either. Example: PUT: https://integration.visma.net/API/controller/api/v1/inventoryReceipt/2700193
Headers: {
Accept: application/json
Authorization: <hidden>
Accept-Encoding: gzip Accept-Encoding: deflate
Request-Id: |mNxxPaa2S54=.73b6c807_5.
Content-Type: application/json; charset=utf-8
Content-Length: 38
}
{"transferNumber":{"value":"2700188"}}
Response: 204 No Content
Headers: {
Date: Fri, 25 Aug 2023 14:50:32 GMT
Server: Nginx
Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains
ipp-request-id: f8e62102-bed6-49b2-96e7-fc42bdce0789
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=Thu, 24-Aug-2023 14:50:31 GMT; HttpOnly
Expires: -1
}
... View more
18-09-2023
14:09
Hi, The procedure of creating a inventory receipt with a transfer number is fully possible in Visma.NET but when trying to do the same thing with the API there is an unhandled error thrown. Full request: POST: https://integration.visma.net/API/controller/api/v1/inventoryReceipt
Headers: {
Accept: application/json
Authorization: <hidden>
Accept-Encoding: gzip Accept-Encoding: deflate
Request-Id: |lakrQ37sjdI=.b3f622d3_4.
Content-Type: application/json; charset=utf-8
Content-Length: 346
}
{"transferNumber":{"value":"2700198"},"receiptLines":[{"warehouseId":{"value":"10"},"operation":"Insert","inventoryNumber":{"value":"121500"},"quantity":{"value":5.000000}},{"warehouseId":{"value":"10"},"operation":"Insert","inventoryNumber":{"value":"122210"},"quantity":{"value":7.000000}}],"date":{"value":"2023-08-26T12:01:38.8295738+02:00"}}
Response: 500 Internal Server Error
Headers: {
Date: Sat, 26 Aug 2023 10:01:43 GMT
Server: Nginx
Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains
ipp-request-id: 6910054c-2769-4f0b-9b48-1a7fb3cf73dc
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=Fri, 25-Aug-2023 10:01:42 GMT; HttpOnly
Connection: close
Transfer-Encoding: chunked
Content-Type: application/json; charset=utf-8
Expires: -1
}
{"message":"VismaId: 6910054c-2769-4f0b-9b48-1a7fb3cf73dc. Error creating inventory receipt Error: An error in processing of field TransferNbr: Object reference not set to an instance of an object.."}
... View more
Activity Feed for MarcusHedlund
- Posted Re: Inaccurate data results when using lastModifiedDateTime on Forum in Developers Visma.net. 10-01-2025 14:59
- Posted Inaccurate data results when using lastModifiedDateTime on Forum in Developers Visma.net. 12-12-2024 15:48
- Posted Re: KitAssembly Update - Error: 'tstamp' cannot be empty. on Forum in Developers Visma.net. 12-04-2024 08:12
- Posted Sv: KitAssembly Update - Error: 'tstamp' cannot be empty. on Forum in Developers Visma.net. 21-03-2024 13:02
- Posted KitAssembly Update - Error: 'tstamp' cannot be empty. on Forum in Developers Visma.net. 21-03-2024 09:20
- Posted Re: Potential invalid validation (Purchase receipt) on Forum in Developers Visma.net. 21-09-2023 13:09
- Posted Potential invalid validation (Purchase receipt) on Forum in Developers Visma.net. 20-09-2023 14:10
- Posted Re: Unhandled error creating a inventory receipt with a transfer number on Forum in Developers Visma.net. 18-09-2023 15:45
- Posted Unhandled error creating a inventory receipt with a transfer number on Forum in Developers Visma.net. 18-09-2023 14:09