About Gabriella Hennings

Daniel Nelin · ‎17-01-2025

Hi. We have followed the instructions in the documentation on how to enable webhooks. We have added a subscription to my dev account for the “supplier_changed” event with a temporary test webhook uri. But after creating and updating a supplier via the integration.visma.net web api no notification was added. We also tested changing a supplier via the finance.visma.net application interface and still nothing happened. Is there something else that needs to be activated for the event to be triggered on change? Is the notification sent out immediately upon change or is it scheduled to certain times? Maybe more seldom for the test environments? We cannot find anything about this in the documentation. /Daniel

Sandra Anté · ‎08-02-2024

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

Gabriella Hennings · ‎08-02-2024

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.

Gabriella Hennings · ‎29-01-2024

Jag har problem med att vissa anrop i våra integrationer blir blockerade av någon brandvägg i PM. Kollar man i dokumentationen står det att man skall kontakta API support men så vitt jag vet finns det inget speciell API support/utvecklar forum för PM, så jag testar här. detta är akut, då det sker i integrationer som ligger skarpt och anropen går igenom ibland och ibland inte.

Magnus Johnsen · ‎17-01-2024

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

Magnus Johnsen · ‎17-01-2024

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

andreasaulin · ‎19-12-2023

The same again today ... 502 Bad Gateway

Gabriella Hennings · ‎13-12-2023

I see now that i have unfortunately have added same object twice in the array of values, most likely that's what causes the error, but you would really wish for some better error message in the response

MagnusHolen · ‎12-12-2023

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.

Magnus Johnsen · ‎17-01-2024

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

Yıldırım · ‎27-11-2023

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

Magnus Johnsen · ‎21-11-2023

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.

Theis · ‎17-11-2023

Working for us now, thank you.

Magnus Johnsen · ‎17-11-2023

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

Yıldırım · ‎30-06-2023

[Release Notes] - Sales Order Service API 1.0.14.638

Cristian Gherghinescu · ‎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.

Gabriella Hennings · ‎09-06-2023

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

Gabriella Hennings · ‎15-05-2023

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?

JoLu · ‎05-05-2023

+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.

Yıldırım · ‎19-04-2023

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

Gabriella Hennings · ‎14-04-2023

Hej vi har problem med att "projekt uppdaterat"-datum (Senast ändrat datum) inte alltid ändras/uppdateras när man ändrar någon information på projekten. det gör det väldigt svårt och omständligt att fånga upp ändringar i projekt ur ett utvecklarperspektiv (genom API:et) när man endast vill hämta förändrade projekt. (ohållbart att hämta alla projekt varje gång när det rör sig om väldigt mycket projekt i installationerna) Datumet ändras exempelvis inte när man uppdaterat projektet med nyckelord eller när man ändrar något i faserna. (det går visserligen att får ut ändrade faser separat genom API:et men då får man hämta alla ändrade faser och sen till vilket projekt det hör, vilket också känns ganska omständligt.) Båda dessa värden hör ju ihop med projektet och bör rimligtvis trigga att projektet har förändrats. projekt utan nyckelord projekt där jag precis lagt till nyckelord, datumet är det samma och det går inte fånga upp att projektet har förändrats.

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.

Gabriella Hennings · ‎03-04-2023

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.

Yıldırım · ‎29-03-2023

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.

Magnus Johnsen · ‎20-03-2023

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

AliMKhan · ‎17-03-2023

The issue seems to have been on one of the IIS server that was handling API calls. For some reason it was not able to connect to the cache, whilst other servers were able to connect at the same time. We suspect that there were too many connections open on that server for some reason. At the moment everything is looking normal and we will monitor the status closely. Sorry for the inconvenience.

Magnus Johnsen · ‎25-01-2023

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.