Par Ronald de Jong

Sandra Anté · ‎03-05-2024

Hi, There has been an issue with this previously but it should have been resolved in version 8.27. We can confirm on our end that when you are using custom reports they are not printed correctly. Please contact you local support for further investigation: https://community.visma.com/t5/Forum-in-Developers-Visma-net/Contacting-Visma-Partner-Service-Visma-net-ERP-Support/td-p/270141 Kind regards Sandra

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

andreasaulin · ‎19-12-2023

The same again today ... 502 Bad Gateway

Yıldırım · ‎14-12-2023

Hello, according to our investigation this is related to a cache issue, that user which has been created for the Service type app on the fly is not immediately synced with the company that request has been made, therefore, usually a day helps to get this resolved upon server cache cycle. However, we're working to fix this, as the behaviour explained above is not feasible.

Re: Shipment confirmation report uses wrong layout...

Re: Bad Gateway messages when making calls to the ...

Re: Bad Gateway messages when making calls to the ...

Re: 500 Error in every API call, Visma.NET service...

Re: 500 Error in every API call, Visma.NET service...

Re: POST Supplierinvoice using new authentication ...

Noderīgas saites

Mūsu risinājumi

Seko mums