About adrianm

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

Hi,could you please share your payload with us ? (developersupport@visma.com) Thanks.

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.

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.

adrianm · ‎13-04-2023

Another user has updated 'APRegister' line. - this usually means that userA tries to modify the APRegister but the APRegister has an older version (because UserB changed the APRegister before) in other words, UserA is working on an old version of APRegister. Can you please stop spreading this myth. That scenario might make sense in the GUI but in the API the message just means "The backend crashed without error message".

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.

Magnus Johnsen · ‎24-03-2023

Hi, Thank you we'll forward this to the development team.

adrianm · ‎20-03-2023

Can't you restore the older version where it did work, at least in V2? (or even better, add the "Destination Warehouse" property) I must also say the error reporting in V3 is really bad. Have now had two difference cases where it just returns "internal server error" without any message.

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

Alright, thanks for the confirmation then !

Yıldırım · ‎20-02-2023

Thanks for the confirmation Jolu

Yıldırım · ‎20-02-2023

Hi Adrian, release notes are prepared & shared as usual there are no changes. Are you referring to the swagger UI update ?

Yıldırım · ‎20-02-2023

Hello, are you still experiencing the issue ?

Lindstromer · ‎07-02-2023

Thank you Magnus, it started working after adding the role via Visma.net admin. To be honest, it does seem like Visma needs to step up and have a more professional process when it comes to deploying new releases. Nothing is mentioned in release notes whatsoever about a new version of Swagger, how to fix access issues or even sending it out beforehand about the change. Would be great if that wasn't found out by posting on the forum and waiting 4 days.

Magnus Johnsen · ‎02-02-2023

Hi, If the company was created recently the error will most likely dissapear by itself, previous cases where we have seen this type of error they have affected new companies and the issue has generally been resolved within 24hrs.

Florian Haase · ‎02-02-2023

We are using ngrok a lot. This also has a web-interface and a great way to see if the webhook is triggered and also the payload of the webhook message. Florian

SKAU AS · ‎01-02-2023

I see this issue on one company.

adrianm · ‎30-01-2023

We sometimes have webhooks with very different functionality on e.g. sales order in the same company. Some are listening for status changes while others are listening for actions (menu items). Currently we need to put all this functionality into the same subscription which makes it difficult to maintain and reuse. (or subscribe with different users)

Yıldırım · ‎20-01-2023

This has been registered as a bug and conveyed to the development team. 1) Create Sales Order (Single line) 2) Create Shipment for that salesOrder (Single Shipment line) 3) Shipment status: Open 4) Salesorder status: Shipping 5) PUT - Delete Shipment Line > OK 6) SalesOrder status, still Shipping. If we remove the Shipment Line via Financials ERP UI 7) Sales order status become : Open

Yıldırım · ‎13-01-2023

Hello, this has been reported as an error, and it is currently under review by the team.

adrianm · ‎10-01-2023

Never mind. Today the same requests work fine

Yıldırım · ‎15-12-2022

Hi, we'll check it out.

Snuffsis · ‎06-12-2022

The solution was provided above, and it was just an issue with how swagger prints out examples. If it isn't too breaking of a change. Since subaccount can contain a varying amount of segments, wouldn't it make more sense that it was a list instead? Something like: [ { "id": "string", "value": "string" }, { "id": "string", "value": "string" } ]

Magnus Johnsen · ‎28-11-2022

Hi! We'll will check this internally. If I'm not mistaken, the applications under your applications are the applications where you have a role assigned, so most likely your own and your teams, but we'll doublecheck this as well. Thank you.

Yıldırım · ‎19-10-2022

Hello, this was related to the incident https://status.visma.com/incidents/wn72zymc4cjn

Yıldırım · ‎04-08-2022

The fix has been released in Visma.Net API 9.08.0

Svar: Error message when posting Journal Transacti...

Svar: Error message "Invalid token"

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

Re: Message: Another user has updated the 'APRegis...

Svar: Internal server error when creating sales or...

Re: Non-standard ETag header

Re: Can't create transfer order

Svar: Delete sales person returns sql error

Svar: Issues for end users with the new Visma Conn...

Re: What is the new release procedure?

Re: 25% of calls to journal transcation fails

Svar: Visma.Net updated today?

Re: 25% of call to journaltransaction endpoint ret...

Sv: Is it possible to see the webhook response?

Re: Webhoook resourceURi

Allow more than one webhook per event

Re: Deleting lines on shipment puts order in stran...

Re: Paging in SalesOrderApi

Svar: Can't create order in one company, some kind...

Re: Response compression does not work with batch

Re: SalesOrder V3 subaccount formatting issue

Re: Sales Order Api questions

Re: Several customers receive 403 on many requests

Re: CustomerCreditNote V2 still returns non existi...

Useful pages

About Visma

Contact us

Follow us