Användarprofil
thingsio
14
Inlägg
0
Gillar
1
Lösning
15-10-2024
11:32
Line numbers are needed to keep an unique identifier for a line. InventoryId does not work as a unique identifier. In some shipments it will be the same InventoryId for several lines. A get-request to catch the lineNumber before the put-request is then what you can do.
If you think lineNumbers is not effective for you and think inventoryId can be useful, you can make a post under the Ideas section of this forum.
... Visa mer
02-08-2024
12:18
Hi, we also have a need to link directly to for example: purchase receipt orders, inventory adjustments etc. Because we pull information from Visma API's in other apps. we also want to link directly from other apps. to make it more convenient for users. For me the second part of the URL is pretty unclear: https://finance.visma.net/1011011001 This number changes once and a while and I don't think it's a version number which can be found in the Swagger documentation. If it can be found in the swagger, to what exactly are you referring in that documentation? A method or something else?
... Visa mer
29-07-2024
14:13
Visma.net has, if you ask me, not a a very elegant way to handle batch adjustments etc. When you offer for example and inventory adjustment through the API with 250 products it will block the whole adjustment if one product isn't in Visma.net. It would be great to have one of these solutions: - send a prameter to switch off the validation of the product ID and ignore non existing products; - report invalid ID's in the response. This would make the API overall more convenient. Check our blog for some Visma.net lowcode API samples: things.io
... Visa mer
14-06-2024
08:47
For suggestions for improvement, we recommend that you create a post in the Ideas section of the forum. This allows other users to vote for your issue, which raises the urgency the development team will have when evaluating your suggestion.
... Visa mer
11-04-2024
08:22
Hi! To do multiple adjustments you add as many of the "issueLines"-objects as you wish in the array of the issueLines.
{
"issueLines": [
{
"operation": "Insert",
"tranType": {
"value": "Issue"
},
"branchNumber": {
"value": "11"
},
"warehouseId": {
"value": "gro"
},
"lineNumber": {
"value": 1
},
"inventoryNumber": {
"value": "10001"
},
"quantity": {
"value": 5
},
"reasonCode": {
"value": "2"
}
},
{
"operation": "Insert",
"tranType": {
"value": "Issue"
},
"branchNumber": {
"value": "11"
},
"warehouseId": {
"value": "gro"
},
"lineNumber": {
"value": 2
},
"inventoryNumber": {
"value": "10001"
},
"quantity": {
"value": 5
},
"reasonCode": {
"value": "2"
}
}
]
}
Hope this answered your question. Kind regards Sandra Anté
... Visa mer
31-08-2023
13:40
Hello,
tested the case again today, I'm able to POST Supplier Invoice without receiving Branch not found error. If you're still receiving the error, we might need to specifically check your company & integration setup, so please contact us via developersupport@visma.com and share your companyID & Application details from the developer portal.
Thanks.
... Visa mer
14-06-2023
08:05
Hi, We use https://integration.visma.net/API/controller/api/v1/inventoryissue and the following data according to the documentation: { "issueLines": [{ "operation": "Insert", "tranType": { "value": "Issue" }, "warehouseId": { "value": "gro" }, "lineNumber": { "value": 0 }, "inventoryNumber": { "value": "13003" }, "quantity": { "value": 7 }, "uom": { "value": "STUK" }, "reasonCode": { "value": "2" } }], "date": { "value": "2023-05-03T10:07:16.563" } } For any logistics company it is really important to be able to see a date when an Inventory issue is changed. Can we get back to the original problem? How can we change the inventory by using the API and also show a date when that is done? Cheers and thanks!
... Visa mer