About Stefan Hult

Stefan Hult · ‎09-01-2023

Hi Refering to "Webhook received multiple times" We have exactly the same problem as Anders at Taventus. Sometimes when the customer confirm a shipment on a Sales Order, Visma sends us two identical webhooks. In the GUI we can only see one webhook has been sent. I have tested this on different companies with the same result. What I notice is that the error is intermittent. I can't find the reason why sometimes we get one webhook and sometimes two. Just to give some example, I performed a test just before I sent this message. This is the only event I have: I created two sales order for the same customer and the same item. I shipped both of them and confirmed. From the first one I got two webhooks, and for the second one I got one webhook. This is the first confirmation, with the two webhooks and the messages from Visma GUI: [{"notificationId":"22d61db4-3070-417f-b858-1271d7d2627d","contextId":"4011658","event":"shipment_changed","relativeResourceUri":"api/v1/shipment/000028","resourceUri":"https://integration.visma.net/API/controller/api/v1/shipment/000028","status":"Confirmed","timeStamp":638088761818270000}] [{"notificationId":"22d61db4-3070-417f-b858-1271d7d2627d","contextId":"4011658","event":"shipment_changed","relativeResourceUri":"api/v1/shipment/000028","resourceUri":"https://integration.visma.net/API/controller/api/v1/shipment/000028","status":"Confirmed","timeStamp":638088761818270000}] {"EntityId":"1d8ce3c5-6266-4557-90b9-6f6f9161eae5","NotificationId":"22d61db4-3070-417f-b858-1271d7d2627d","Event":"Shipment_Status_Changed","DocumentStatus":"Confirmed","TimeStamp":"638088761818270000","EntityLocation":"api/v1/shipment/000028"} And the second one: [{"notificationId":"2309d12e-c45c-49e2-8643-04d10dc2e14b","contextId":"4011658","event":"shipment_changed","relativeResourceUri":"api/v1/shipment/000029","resourceUri":"https://integration.visma.net/API/controller/api/v1/shipment/000029","status":"Confirmed","timeStamp":638088762659670000}] {"EntityId":"e0bd2389-a439-4167-aeea-76603bac0945","NotificationId":"2309d12e-c45c-49e2-8643-04d10dc2e14b","Event":"Shipment_Status_Changed","DocumentStatus":"Confirmed","TimeStamp":"638088762659670000","EntityLocation":"api/v1/shipment/000029"} And this is the details from Webhook.site: Can you please look into case again, I'm sure other partner will run into the same problem. /Stefan

Stefan Hult · ‎30-08-2022

It Works for us. Thanks.

Stefan Hult · ‎30-08-2022

We got the same error, but for DELETE You don't have permission to access this resource.

Stefan Hult · ‎19-08-2022

It is very useful to have overridenumberseries on several endpoints. But we have customers with POS systems where we want to import the receipt number into Visma.Net. The easiest and safest way, to avoid duplicates and to simplify searches, is to use the referenceId field for the receipt number. There is already a setting for the possibility to import manual numbers in the number series setting. What is missing is the overridenumberseries option. This applies to both CashTransaction and CashSales. /Stefan

Stefan Hult · ‎24-05-2022

After contact with Yildirim we realise there isn't any shortcut here. This customer has a substantial number of transfer order lines and create them took a long time. We then decided to use the background functionality, and it works fine. New API feature: "erp-api-background" operation - Visma Community

Stefan Hult · ‎20-05-2022

Hi Yildirim Thank, then we know we don't have to spend more time trying to make PUT to work. Number of transferOrderLines is between 70 -250 lines. The test we have used is on 74 lines. We have tried different timeout, 10, 20 and 50 minutes. Details will come by mail from the developer. Thanks.

Stefan Hult · ‎18-05-2022

Hi We have now learned, that when we POST a receipt connected to a transfer order we use the following, and it works fine. Thanks Magnus. Now comes part 2, we want to use PUT to add new lines. We use the previous example and add the receipt number and the new line number. And get this error back. We have tested different combination, but it all ends up with telling us the order number is missing. Now, for those who wonder why we want to use PUT. We have discovered that if you have a transferorder with many lines, you get a TimeOut when you try to POST the receipt. What we have seen is that somewhere between 10 and 20 lines work. If you have more that that you get a TimeOut. We know for sure that if we POST a receipt of 10 lines it works. That's why we have to split the receipt and send the rest of the lines, 10 lines at a time, with a PUT. Conclusion We have two problems here. 1. Timeout in POST if a large number of lines. 2. Cant add lines to an existing receipt using PUT.

Stefan Hult · ‎29-04-2022

Okay I sum up the conversation. What you mean, is that we can't use the action/addpurchaseorder endpoint to automatically add the transfer order and all it's lines. With other words, the same routine that works in the GUI. Instead we have to POST a receipt with all information from the transferOrder?

Stefan Hult · ‎29-04-2022

Hi Magnus Just to be sure, what you described, isn't that step 1 and not step 2?

Stefan Hult · ‎28-04-2022

Hi In the GUI I can connect a transferorder to a Purchase Receipts, and as you see below it works fine. If I try the same in the API it doesn't work as expected. POST https://integration.visma.net/API/controller/api/v1/PurchaseReceipt/2500189/action/addpurchaseorder { "purchaseOrders" : [ { "orderNbr" : "4300046" } ] } Error adding purchase orders to receipt: Open order with number 4300046 could not be found" It doesn't matter is I use the ordertype or not. I have tested different combinations, but non of them work.

Stefan Hult · ‎25-04-2022

Hi Magnus These just got weird... First problem I followed your instructions and deleted a record and tried to Post it: DELETE https://integration.visma.net/API/controller/api/v1/discount/TEST2/1 POST https://integration.visma.net/API/controller/api/v1/discount { "discountCode": { "value": "TEST2" }, "series": { "value": "1" }, "discountBreakpoints": [ { "operation": "Insert", "lineNbr": { "value": 1 }, "pendingBreakAmount": { "value": 5 }, "pendingDate": { "value": "2022-04-25T06:40:34.062Z" }, "pendingDiscountPercent": { "value": 10 } } ] } Using the operator "Update" didn't work for me. But using "Insert" worked. But what happen?? The series is not "1" but "TEST20001"! Second problem When it comes to adding lines. Adding new lines work fine, but the result is not so good. Give you a new series instead. I can't imagine this is correct. 🙂

Stefan Hult · ‎22-04-2022

Hi I want to change prices with the Discount endpoint. The scenario is the following. Marked in red are the information I want to change. Using this update: Gives me the anwer: "message" : "VismaId: 8564dedf-1e67-4a45-8f69-49671b637b65. Handle(Visma.net.ERP.Api.AR.CommandModel.Commands.ChildCommands.UpdateCustomerDiscountLineCommand cmd) not found" And it doesn't mater if I use "pendingdiscountAmount" etc. I get the same error message. Changing the "Operator" to "Insert", gives me another error: "message" : "Field 'Pending Discount Amount' cannot be updated because is not visible or editable." I get the same error if I tries to POST a new record. Any suggestions?

Stefan Hult · ‎19-04-2022

Hi Yildrim Problem solved. We noticed now that the payment was created on an other branch than the credit note. That's why the release couldn't be done. If this is an error or not I don't know, because release can be done in the GUI. But anyway. We close this case.

Stefan Hult · ‎14-04-2022

Hi Yildirim Yes, I have. And it works exactly as supposed. /Stefan

Stefan Hult · ‎14-04-2022

Hi The case is the following: A customer is buying something in a shop. He pays with credit card and we then generate a customerInvoice from the card transaction, and makes a payment though the API. A day later he comes back and wants to return what he has bought. We then generate a customerCreditNote, and make a Refound. Here comes the tricky part. This is what we send, using the customerPayment endpoint. { "referenceNumber" : { "value" : "10041722" }, "type" : { "value" : "Refund" }, "customer" : { "value" : "KONTANT" }, //"applicationDate": {"value": "2021-06-23T14:51:21.138Z"}, "paymentAmount" : { "value" : 6277 }, "paymentMethod" : { "value" : "03" }, "cashAccount" : { "value" : "1933" }, "branchNumber" : { "value" : "103" }, "paymentLines" : [ { "operation" : "Insert" , "documentType" : { "value" : "CreditNote" }, "refNbr" : { "value" : "10041722" }, "amountPaid" : { "value" : 6277 } } ] } This works fine and a payment transaction is generated in Visma.Net. We now wants to release the payment using customerPayment/14000002/action/release endpoint. { "type" : { "value" : "Refund" } } And the answer we get back is: { "actionId" : "40f2733f-2e5e-4260-81d2-a787959beb6a" , "actionResult" : "InProcess" } It seams to work, but nothing happens in Visma.Net. Checking a couple of hours later, still nothing have happen on the payment.

Stefan Hult · ‎14-03-2022

We have problem with an integration when the number series are the same in JournalTransaction. If we want to Get the AR transaction we can't use the: /controller/api/v2/journaltransaction/{journalTransactionNumber} because that call gives us only the GL transaction. We have to use the: /controller/api/v2/journaltransaction and add it to a dictionary to find the AR transaction we are searching for. I have two suggestions to change the API 1. Do the same as on SalesOrder (/journaltransaction/AR/100005) add the module name to the call. 2. Return all records with the same number, no matter what the module is.

Stefan Hult · ‎27-01-2022

In this example a user, for some reasons, have entered a zip code, on a customer, with a space in middle. And ignored error messages. The same problem can happens if an integration are adding customers. If you now tries to POST an customerInvoice you will get an error message telling you that: { "message" : "VismaId: 04be2aff-ef32-4dd7-9b58-c04da25a4603. Object reference not set to an instance of an object." } My suggestion is to make this more accurate, the problem now is to find the error. Stefan Hult Amesto Solutions AB

Stefan Hult · ‎29-11-2021

Hi Allan The only solution we found was to wait for the shipping, there you can find both the IN och UT warehouses. /Stefan

Stefan Hult · ‎26-11-2021

In shipment, action menu, and Update inventory.

Stefan Hult · ‎25-11-2021

In shipments, you can setup the Transfer Type to 2-Step. This is use full when you use Transfer orders. If you do that, you receive an extra step in the Action menu: "Update IN". And you must use it to update your stock quantity. In the API there are actions confirm- and correct-shipment, but updateInventory is missing. Is it forgotten or is there a other way to handle this? Regards Stefan

Stefan Hult · ‎29-09-2021

Can't find any endpoint giving me the possibilities to Prepare an Invoice from a Sales order. Anyone having a suggestion?

Stefan Hult · ‎23-06-2021

Hi Magnus I have tried to upload the picture in several different ways but it don't work. Here comes a description instead: 1. Go to Sales Order and add a new order 2. Choose the ordertype TR 3. Add a destination wearehouse 4. Add an article and choose the wearehouse from were the article is to be moved. 5. Save the order If you now use this endpoint GET https://integration.visma.net/API/controller/api/v1/salesorder/tr/{orderNo} You get the wearehouse on the orderline, but no information about the destination wearehouse.

Stefan Hult · ‎17-06-2021

In the GUI for sales order, there is a drop-down menu with the option to create an invoice based on sales order. I can't find it in the API. Is it on the development list? /Stefan

Stefan Hult · ‎17-06-2021

The saleorder is registered manually in Visma.Net with ordertype "TR". After registration the integration process the orders by the API. This is the GET for salesorder with transactiontype "TR". GET https://integration.visma.net/API/controller/api/v1/salesorder/tr/000024 authorization: Bearer 1fe4bb0c-4ea6-45a0-98ff-814603b4ae72 ipp-company-id: xxxxxxx Content-Type: application/json The response looks like this, where I am missing the destination. I presume it should be in ”preferredWarehouse” field. { "project": 0, "soBillingContact": { "overrideContact": false, "contactId": 314443, "name": "TEST xxxxxxxx AB", "attention": "" }, "soBillingAddress": { "overrideAddress": false, "addressId": 345952, "addressLine1": "xxxxxxx", "addressLine2": "", "postalCode": "11521", "city": "Stockholm", "country": { "id": "SE", "name": "SVERIGE" } }, "customerVATZone": {}, "terms": {}, "salesPerson": {}, "owner": {}, "soShippingContact": { "overrideContact": false, "contactId": 314446, "name": "Butiken" }, "soShippingAddress": { "overrideAddress": false, "addressId": 345955, "addressLine1": "xxxxxxxx", "city": "Stockholm", "country": { "id": "SE", "name": "SVERIGE" } }, "schedShipment": "2021-06-17T00:00:00", "shipSeparately": false, "shipComplete": "BackOrderAllowed", "cancelBy": "2021-07-17T00:00:00", "canceled": false, "preferredWarehouse": {}, "shipVia": {}, "fobPoint": {}, "priority": 0, "shippingTerms": {}, "shippingZone": {}, "residentialDelivery": false, "saturdayDelivery": false, "insurance": false, "transactionType": { "id": 0, "description": "Ingen (exkluderad)" }, "paymentMethod": {}, "lines": [ { "operation": "Issue", "freeItem": false, "requestedOn": "2021-06-17T00:00:00", "shipOn": "2021-06-17T00:00:00", "shipComplete": "BackOrderAllowed", "undershipThreshold": 100.000000, "overshipThreshold": 100.000000, "completed": false, "markForPO": false, "taxCategory": "01", "commissionable": false, "lineNbr": 1, "sortOrder": 1, "inventory": { "number": "20130001-S", "description": "xxxxxxxx" }, "warehouse": { "id": "1 ", "description": "Packing" }, "uom": "STYCK", "quantity": 1.000000, "qtyOnShipments": 0.000000, "openQty": 1.000000, "unitCost": 43.470000, "unitPrice": 0.000000, "unitPriceInBaseCurrency": 0.000000, "discountPercent": 0.000000, "discountAmount": 0.0000, "manualDiscount": false, "discUnitPrice": 0.000000, "extPrice": 0.0000, "unbilledAmount": 0.000000, "lineDescription": "xxxxxx", "branchNumber": { "number": "1", "name": "xxxxxx" }, "attachments": [] } ], "shipments": [], "orderType": "TR", "orderNo": "000024", "status": "Open", "hold": false, "date": "2021-06-17T00:00:00", "requestOn": "2021-06-17T00:00:00", "customer": {}, "location": { "id": "MAIN", "name": "Primary Location" }, "currency": "SEK", "orderTotal": 0.0000, "orderTotalInBaseCurrency": 0.0000, "vatTaxableTotal": 0.0000, "vatTaxableTotalInBaseCurrency": 0.0000, "vatExemptTotal": 0.0000, "vatExemptTotalInBaseCurrency": 0.0000, "taxTotal": 0.0000, "taxTotalInBaseCurrency": 0.0000, "exchangeRate": 1.00000000, "discountTotal": 0.0000, "discountTotalInBaseCurrency": 0.0000, "lastModifiedDateTime": "2021-06-17T11:35:32.093", "branchNumber": { "number": "1", "name": "xxxxxxxx" }, "attachments": [] } This is the createShipment routine POST https://integration.visma.net/API/controller/api/v2/salesorder/000024/action/createShipment authorization: Bearer 1fe4bb0c-4ea6-45a0-98ff-814603b4ae72 ipp-company-id: xxxxxx Content-Type: application/json { "orderType": "TR", "returnShipmentDto": true, "shipmentDate": "2021-06-20T06:16:23.836Z", "shipmentWarehouse": "1" } The respond is the following. Here we have from and to warehouse, witch is correct. { "referenceNumber": "000016", "shipmentDto": { "shipmentNumber": "000016", "shipmentType": "Transfer", "status": "Open", "hold": false, "operation": "Issue", "shipmentDate": "2021-06-20T06:16:24", "customer": { "internalId": 2461, "number": "1 ", "name": "xxxxxxxx" }, "location": { "id": "MAIN", "name": "Primary Location" }, "fromWarehouse": { "id": "1 ", "description": "Packing" }, "toWarehouse": { "id": "2 ", "description": "Butiken" }, "currencyId": "SEK", "shippedQuantity": 1.000000, "shippedWeight": 0.000000, "shippedVolume": 0.000000, "packagesWeight": 0.000000, "controlQuantity": 1.000000, "deliveryAddress": { "overrideAddress": false, "addressId": 345955, "addressLine1": "xxxxxxx", "city": "Stockholm", "country": { "id": "SE", "name": "SVERIGE" } }, "deliveryContact": { "overrideContact": false, "contactId": 314446, "name": "Butiken" }, "residentialDelivery": false, "saturdayDelivery": false, "useCustomerAccount": false, "insurance": false, "freightCost": 0.0000, "freightAmt": 0.0000, "transactionType": { "id": 0, "description": "Ingen (exkluderad)" }, "modeOfTrasport": { "id": 10, "description": "Unknown" }, "container": false, "shipmentDetailLines": [ { "lineNumber": 1, "orderType": "TR", "orderNbr": "000024", "inventoryNumber": "20130001-S", "freeItem": false, "warehouse": { "id": "1 ", "description": "Packing" }, "location": { "id": "1", "name": "Standard" }, "uom": "STYCK", "shippedQty": 1.000000, "orderedQty": 1.000000, "openQty": 0.000000, "lotSerialNbr": "", "description": "xxxxxxxx", "allocations": [ { "lineNbr": 2, "itemId": "20130001-S", "location": { "id": "1", "name": "Standard" }, "lotSerialNumber": "", "quantity": 1.000000, "uom": "STYCK", "description": "xxxxxxx" } ], "orderLineNbr": 1 } ], "shipmentOrderLines": [ { "orderType": "TR", "orderNbr": "000024", "shippedQty": 1.000000, "shippedWeight": 0.000000, "shippedVolume": 0.000000, "note": "" } ], "lastModifiedDateTime": "2021-06-17T11:42:15.2", "note": "", "metadata": { "totalCount": 1, "maxPageSize": 1000 } }, "actionId": "fee4fe10-11fe-4091-a5a1-b31ec94f6841", "actionResult": "Done" }

Stefan Hult · ‎16-06-2021

https://integration.visma.net/API/controller/api/v1/salesorder/tr/000015

Stefan Hult · ‎16-06-2021

Sorry, I switched the TO and FROM warehouse in my topic above. /Stefan

Stefan Hult · ‎15-06-2021

Transfer order is used for moving products between different warehouses. What I can see is that orderlines works fine. We got the warehouse, where to move the products. But, from what warehouse should we take the products? The field is there but it's empty. See red below. /Stefan "schedShipment": "2021-06-15T00:00:00", "shipSeparately": false, "shipComplete": "BackOrderAllowed", "cancelBy": "2021-07-15T00:00:00", "canceled": false, "preferredWarehouse": {}, "shipVia": {}, .......... "lines": [ { "operation": "Issue", "freeItem": false, "requestedOn": "2021-06-15T00:00:00", "shipOn": "2021-06-15T00:00:00", "shipComplete": "BackOrderAllowed", ........ "lineNbr": 1, "sortOrder": 1, "inventory": { "number": "20130001-XS", "description": "T-SHIRT Unisex black" }, "warehouse": { "id": "1 ", "description": "Packing" }, "uom": "STYCK",

Stefan Hult · ‎10-06-2021

Hi In the "Visma.net ERP API Webhooks Setup ...." documentation there is said that: Notifications are sent only once. If the receiver (subscription webhookUri) is not available the notification is not automatically resent. In an answer Yildirim gave to Timo_O a year later, 2021-01-29, he mentions that: Such as checking registered hook_uri > attempts to deliver > if it fails, trying up to 5 times > if it's still not delivered then log the notification so that can be fetched via "/notification/failed" endpoint. Now to the questions: - Are we talking about different things here? - Is there a retry mechanism for webhooks that fails? - And if so, what is the time lapse between the retry?

Stefan Hult · ‎09-06-2021

Hi Insert LandedCost on a Receipt with following endpoint https://integration.visma.net/API/controller/api/v1/PurchaseReceipt/000005 causes this error: VismaId: a8fb3f26-b9bd-455a-87ff-ec022b39f954. Error updating purchase receipt. Object reference not set to an instance of an object. Tried to isolate the error but nothing helps. { "landedCost" : [ { "operation" : "Insert" , "landedCostCode" : { "value" : "PACKING1" }, "apBillDate" : { "value" : "2021-06-08T16:44:28.012Z" }, "currency" : { "value" : "SEK" }, "locationId" : { "value" : "Primär" }, "description" : { "value" : "Kostnad för packning" }, "supplierID" : { "value" : "50010" }, "amount" : { "value" : 100 }, "apDocType" : { "value" : "Check" }, "inDocType" : { "value" : "Undefined" }, "inRefNbr" : { "value" : "1600004" }, "postponePurchaseInvoiceCreation" : { "value" : true } } ] }

Stefan Hult · ‎19-04-2021

Currently, Employee Endpoint is missing the function to POST & PUT and GET attributes from employee. We also need to be able to filter the GET request based on Employee "Attributes" values.

Webhook received multiple times when shipment is c...

Re: "You don't have permission to access this reso...

Re: "You don't have permission to access this reso...

overrideNumberSeries on CashTransaction and CashSa...

Svar: Transfer orders and receipts, part 2

Re: Transfer orders and receipts, part 2

Transfer orders and receipts, part 2

Re: Transferorder and receipt

Re: Transferorder and receipt

Transferorder and receipt

Svar: Strange error codes when updating Discount

Strange error codes when updating Discount

Svar: Release of refunded payment don't work

Svar: Release of refunded payment don't work

Release of refunded payment don't work

GET JournalTransaction improvement

Missing error message for zipcode

Re: Missing warehouse on Transfer order

Re: Missing actions in shipping

Missing actions in shipping

Prepare Invoice from SalesOrder

Svar: Missing warehouse on Transfer order

Create invoice from Sales order

Svar: Missing warehouse on Transfer order

Svar: Missing warehouse on Transfer order

Svar: Missing warehouse on Transfer order

Missing warehouse on Transfer order

Retry mechanism for webhook

Insert LandedCost causes an error

Employee attributes

Useful pages

About Visma

Contact us

Follow us