About Kjetil Ringstad

Kjetil Ringstad · ‎14-09-2022

Hi We need to update the group fields in the orderDocument table, but it doesn't seem to have any available methods to do this the same way you would update the order table. What is your suggestion on how to do this?

Kjetil Ringstad · ‎22-03-2022

When doing a POST to SalesOrder, can the fields origOrderNbr and origOrderType be used freely, or are there any logic / business rules tied to those fields?

Kjetil Ringstad · ‎21-03-2022

Can you please consider exposing product cross references in the nextgen inventory summary endpoint GET/api/v3/Inventory ? If you could expose it the same way the attributes are exposed, a separate call to fetch these from the products are prevented.

Kjetil Ringstad · ‎14-02-2022

It looks like it wasn't logged on our side. But the timestamp is 2022-02-14T10:40:41 , companyid 2693113

Kjetil Ringstad · ‎14-02-2022

This is a shipment update, POST /controller/api/v1/shipment/{shipmentNumber}/action/confirmShipment Confirm shipment operation When retrying we are informed the shipment has already been confirmed. But that's not the issue itself here. Should SQL Deadlock messages really be returned through the API? We have no control over which operations you have completed or not on your side.

Kjetil Ringstad · ‎14-02-2022

Hi At a few occasions SQL error messages are being returned in the response from the API with a statuscode 400: {"message":"Transaction (Process ID 1579) was deadlocked on lock resources with another process and has been chosen as the deadlock victim. Rerun the transaction."} Are you rerunning these transactions or should we resend them?

Kjetil Ringstad · ‎07-02-2022

We're experiencing the same issue across several customers / companies

Kjetil Ringstad · ‎11-12-2021

As far as we can see it's better now, thank you.

Kjetil Ringstad · ‎08-12-2021

Can workgroup (marked yellow below) please be exposed on the shipment API endpoints?

Kjetil Ringstad · ‎08-12-2021

The timeouts are still happening sporadically on the same endpoints. latest at 10:45, 11:07, 12:18,12:25 , companyId 2693113

Kjetil Ringstad · ‎08-12-2021

Thank you. Looks like it's related to shipments. between 0930 and 10:00 today GET /controller/api/v1/shipment/{shipmentNbr} POST /controller/api/v1/shipment/{shipmentNumber}/action/confirmShipment

Kjetil Ringstad · ‎08-12-2021

Hi guys Lots of timeouts and 502s now from several endpoints. Can you please look into it?

Kjetil Ringstad · ‎29-11-2021

@Visma , can you please explain what happened and why? As andreasaulin says, traffic shouldn't come as a surprise as it's cyber monday.

Kjetil Ringstad · ‎29-11-2021

We're experiencing the same issue for most of our companies. The Swagger page is also looking a bit weird now, missing a lot of endpoints. And still status.visma.com is showing no problems for the API...

Kjetil Ringstad · ‎18-11-2021

Please expose lead time (Leveringstid) in the customer endpoints. (yellow markings in the image below) This field is needed to do proper calculations of delivery dates. Since it's not exposed to the API the only option is to also have it as an attribute.This seems unnecessary since it's already a separate field for it in the GUI.

Kjetil Ringstad · ‎16-11-2021

Please consider the possibility to expose serial no / lot no and expire date on API calls to the intentory adjustments endpoints. POST / GET : /controller/api/v1/inventoryadjustment These fields are available in the GUI. To be able to do proper adjustments for customers in the food industry , these are required fields.

Kjetil Ringstad · ‎27-10-2021

I can confirm this has been an issue for some (not all) of our customers the last few days. When querying customerinvoices using lastModifiedDate no data was returned from Visma.net.

Kjetil Ringstad · ‎08-10-2021

We need the possibility to do a lookup from customer invoices to the orders and shipments, as in GUI. For the customerinvoice endpoints, is it possible to expose ordertype , orderno and shipmentno ( purchase receipt no for dropshipment orders ) when retrieving the customer invoices? They are displayed in the GUI, but not available through API through the GET endpoints . This means numerous calls to the orders and shipment endpoints are needed to be able to find an invoice reference If these are exposed , numerous calls to iterate shipments and orders to find a specific invoice number are avoided.

Kjetil Ringstad · ‎24-09-2021

Hi Not as far as I can see.

Kjetil Ringstad · ‎23-09-2021

Thank you, company id's for 502 at the times written above 1415473 2137004 For 504 at the times written above: 2693113 client id integrasjonspartner_live

Kjetil Ringstad · ‎23-09-2021

Additional 502 Bad gateway messages posting to the inventory endpoint this morning around 0801 Can Visma please share their thoughts of the last weeks reliability incidents? This is happening a bit too often for comfort now.

Kjetil Ringstad · ‎22-09-2021

Hi We're receiving 504 gateway timeouts today when posting to : POST /controller/api/v1/shipment/{shipmentNumber}/action/confirmShipment and POST /controller/api/v1/shipment This was occuring around 13:22 according to our logs. We do have automatic retries, but such disruptions have huge impact on our customers production environments , leading to delays and goods being sent late from warehouses.

Kjetil Ringstad · ‎20-09-2021

Our logs shows the endpoint was unavailable between 10:34 and 10:51. An explanation would be interesting to see.

Kjetil Ringstad · ‎16-09-2021

Hi Did you get an ETA for this? The customers affected by this are getting impatient.

Kjetil Ringstad · ‎15-09-2021

Hi From 12:36 today we are experiencing multiple 502 bad gateway errors across endpoints along with rejected logins. Can you please look into it. This affects most of our customers.

Kjetil Ringstad · ‎14-09-2021

I don't know if it's related, but the last days we've been experiencing performance loss from the InventorySummary endpoint as well.

Kjetil Ringstad · ‎30-08-2021

Hi, another update as promised. From Aug 5th we see timeouts starting, occuring more often from then 9th and from the middle of the month several occurences, and increasing.

Kjetil Ringstad · ‎23-08-2021

Can we please have an update?

Kjetil Ringstad · ‎20-08-2021

I've received feedback from our customers that when releasing shipments this is happening as well. This has increased in occurences after last upgrade.

Kjetil Ringstad · ‎19-08-2021

I don't have the raw JSON response at the moment, but the response text itself is " Error receiving data: (12002) The operation timed out". As far as we have been able to track it's not timing out on our end.

Updating table orderDocument

Salesorder API fields origOrderNbr and origOrderTy...

Expose cross references in the nextgen inventory s...

Re: SQL Error messages being returned

Re: SQL Error messages being returned

SQL Error messages being returned

Sv: Slow performance and strange errors from API t...

Re: Lots of timeouts from the API now

Expose workgroup on shipment API endpoints

Sv: Lots of timeouts from the API now

Sv: Lots of timeouts from the API now

Lots of timeouts from the API now

Sv: Timeout from the API

Sv: Timeout from the API

Expose lead time on customers

Expose serial no / lot no / expire date on invent...

Sv: lastModifiedDateTime in customerinvoice not wo...

Expose orderno / shipmentno / ordertype on custome...

Re: 504 gateway timeouts today

Re: 504 gateway timeouts today

Sv: 504 gateway timeouts today

504 gateway timeouts today

Sv: Requested URI does not exist: /api/v1/SalesOrd...

Re: Strange error when creating purchase receipts ...

System wide 502 errors and rejected logins

Re: Timeouts from the InventoryTransfer endpoint

Re: Timeouts from the InventoryTransfer endpoint

Re: Strange error when creating purchase receipts ...

Re: Timeouts from the InventoryTransfer endpoint

Re: Timeouts from the InventoryTransfer endpoint

Useful pages

About Visma

Contact us

Follow us