Hi Gabriella, The issue was caused by an improvement allowing partial subaccounts to be used via the API. This has now been deactivated and the development team is working on a fix. Could you please check if this is working for you now? Kind regards Sandra ... View more

HI, I found an email adress to the API support, and got help that way, so problem is solved and the API calls or the scenario are passing through the firewall with OK result as of now. ... View more

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4 ... View more

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4 ... View more

The same again today ...  502 Bad Gateway ... View more

Hi, we are also having this exact issue on a old integration after switching to tennant id authorization. Works fine when authenticating with the old authentication method. ... View more

Hi, We are aware and are looking into it: https://status.visma.com/incidents/xj1qjw02p3w4 ... View more

Hello, the fix has been applied on [Release Notes] - Visma.Net API 9.67.0 - 17.10.2023 ... View more

Hi, Prepare invoice (from sales order) is now available. Does this cover the need in this aswell?   Notice that there is a difference in Prepare invoice in sales order and Prepare invoice in shipments Sales order - Prepare invoice -> Invoice all confirmed shipments related to the sales order Shipment - Prepare invoice -> Invoice only order lines added to the shipment   Thank you.  ... View more

Working for us now, thank you. ... View more

Hi, Is this the full eror message you are getting? Which endpoint are you using? If it's v3, it's most likely related to this: Getting DNS error when posting Salesorder v3 Status: Investigating an issue in Visma.net ERP Sales Order Service ... View more

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. ... View more

This has appeared as an issue again? but this time I get error and inventory not found?   ... View more

Here is how the non-stock kit item looks. All of the components are stock items with lot-tracking:     And here it is on a shipment:   And the allocations, with already pregenerated lots. As you can see, they have different product number too. I can update existing rows here in the allocation, but I can't insert new once through the API.  All of the allocations reference the same shipment row, so therefor i don't understand how it would know the product number of the lot/seriel i would be inserting as a new row.     What am i missing? ... View more

+1 on this from us as well, we are getting this message several times each day for different tenants on different endpoints for the last couple of days, like generalledgertransactions, customercreditnote and generalledgerbalance. We are using clientId/tenantId as well and are checking the expiration time of the token before each call. ... View more

Hello,  please send us the latest version of your JSON and the CompanyID <developersupport@visma.com> ... View more

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.  ... View more

HI  We are also experienceing the same error, some orders just don't work and we just get 500 error in return with, I can POST one order to one customer and then we can POST the same order to another customer and the we receive 500 error with no response message. this feels really unstable. ... View more

Hello,  the error was related to the load balancing and how the requests get distributed when one of the servers have been heavily loaded. We have increased the number of servers, aiming that load will be more evenly distributed. We're currently monitoring the status, and it seems that action helped to resolve the issue. Please let us know if you still receive the error. We're sorry for the standstill this may have caused in your integrations.  ... View more

Hi, Alright, let us know if you still need assistance when they have specified their needs. ... View more

This is planned to be included in the 9.32.0 release [31/1/23]: Previously, the "salesCategories" field in Inventory endpoint returned only sales category description. This has now been changed so that the endpoint will return both the category ID and the category description. ... View more

Hi We solved this issue now, the solution was not to send location o the allocation lines.   brgds Steinar ... View more

I still get this error almost every day.     ... View more

This has been reported to the development team, we'll update you as soon as we have more information. ... View more

Hello,  based on financials company segment / numbering setup white & trailing spaces are encoded to "+" character in the "relativeResourceUri" & "resourceUri" after the inventory id.  We have an improvement case registered in our backlog. However, this is currently not prioritized, we'll update the case and emphasize the issue once again. Trim trailing spaces on the server side before sending the webhook notification. Alternatively, return b64(xxxx) encoded values in the "relativeResourceUri" & "resourceUri" for the objects that contains reserved characters / White & Trailing spaces. Currently, handling the trim method on the client side appears to be the only way to cope with the case. ... View more