About Theis

Oskar Jansson · ‎05-06-2025

Hi, make sure the organization (tenant) has granted the necessary permissions for the events in the Visma App Store: If this isn't the cause of the issue, please provide more details through the Discord server or one-to-one support, as the Developer Forum is now in read-only mode. Country Partner portal Support email Norway & Denmark https://visma-swno.my.site.com/s/api cloud.api.support@visma.com Sweden - api.consulting.se@visma.com Netherlands https://visma-software-nl.force.com/supportportal/s/ - Finland - api.consulting.se@visma.com

Theis · ‎28-03-2025

I always use Insert, I think update only works, if there is already an assigned serial number. Suspect the line number is just a place holder. Please also note, that the line number for allocations, should be written as: lineNbr { "operation": "Update", "lineNbr": { "value": 9 }, "shippedQty": { "value": 1 }

Joni Wolff · ‎04-02-2025

If the order types number series have been setup to default be auto-generated, you can in the API use the field "overrideNumberSeries": true. This way, with the order type, if created from UI it will get an order id generated by the system. And from the API, if the "overrideNumberSeries" is set true and a non-existing "orderId" is provided, the order will be created with the provided order id.

Joni Wolff · ‎01-11-2024

We will fix so that the error does not appear if the default supplier does not have a currency ID set, but until then, as a workaround, setting the currency ID on the supplier will eliminate the error.

Suzdar Ibrahim · ‎12-07-2024

Hi! Given that this is a Norwegian company(?) sales abroad are tax-free. We have no tax zone for the EU at all. Some may have a voluntary registration in Sweden and must calculate Swedish VAT in addition, this is not something we support as standard and may have to be set up in each case. Since you mention sales to the EU, I guess it may be a question of a Swedish client where they have their own tax zones for that. Unfortunately, I don't know the Swedish setup so this is something you have to discuss with them. BR, Suzdar

Theis · ‎31-05-2024

Thank Rozhat, I can see that I need to do expand: Freight, to get those values, thank you. Any way to get it on shipment?

Theis · ‎30-11-2023

Hi Magnus it is working, thank you.

Theis · ‎17-11-2023

Working for us now, thank you.

Joni Wolff · ‎17-10-2023

For the breaking changes we will follow the same guideline as what is today in the Visma.net ERP API, i.e. latest 3 months before. In the closest roadmap we have not planned to introduce createShipment in V3. Could you elaborate a bit more for why it is highly needed in V3? Is it, for example, for the easier use of the API through the sales process or expectation of better performance in that endpoint etc?

Joni Wolff · ‎16-08-2023

Hi! This is a bug, the freight amount should be set to the same as the freight cost when the Shipping term has not been defined, this is not happening at the moment. We have created a case to fix this and release notes will be published when it is fixed.

Yıldırım · ‎05-07-2023

Thanks for the confirmation ! Please let us know if there's more that can be improved 😊

Anonymous · ‎27-06-2023

Hi, Getting back with more details about the problem from 21st of June. Around the interval: 2023-06-21T02:10:00.406+03:00 and 2023-06-21T10:38:26.406+03:00 most of the calls to the Sales Order Service API returned 500. We have restarted the cluster of the service and then calls got back to normal. While investigating the cause of this we noticed that the calls our service makes to another internal service to retrieve information about a tenant are failing with an Unauthorized exception. From the logs it seemed that Authorization header was not included in those calls. Restarting the cluster fixed this problem but we created a task to further investigate why the Authorization header was not included and another case to improve the code to be more resilient when making calls to this internal service. Another action point for us is to improve the monitoring. The current monitoring detected the errors but we did not have any alarms set for a high rate of them. We will implement a warning when the error rate reaches 20% and a critical alarm for Central Operations when the rate reaches 50%. This will allow us to respond faster when something similar might happen.

Magnus Johnsen · ‎13-04-2023

Hi, The development team are solving these issues as they get information on them, if you could send us the json and compnay id we can forward it to the development team for investigation.

Re: Webhooks via Developer Portal

Sv: Can not update lotSerialNbr

Re: Find order type numbering sequence?

Re: (0005-InvalidState) Currency rate not found fo...

Re: Multiple EU VAT rules

Sv: Premium freight in API

Re: https://integration.visma.net/API/controller/a...

Re: Getting DNS error when posting Salesorder v3

Re: Missing field and actions SalesOrder API V3

Re: Salesorder v3 - Freight not included in Order ...

Re: Sales orders V3 created by id

Svar: URGENT! 500 error in salesorder api in GET r...

Svar: SalesOrders v3 - Error 500 on customer, but ...

Useful pages

About Visma

Contact us

Follow us