Over Magnus Johnsen

Magnus Johnsen · ‎27-11-2024

The scheduled maintenance window that was planned for 6th of December has been postponed to the 10th of December. During the release of version 10.29, Visma Net will be unavailable. Please note that this release introduces a breaking change as announced in this post.

Magnus Johnsen · ‎18-11-2024

Due to mandatory changes to the SAF-T report, we are changing the type of two fields in the Account endpoints DTO. The fields affected are PublicCode1 and PublicCode2 and their type will change from Int to String. This change is required from 01.01.2025. To comply with the legal requirements, we are releasing this change faster than our preferred grace period of three months. We are urging you to have a look at your integrations and update this. The changes will be released with version 10.28, planned for the 6th of December 2024 This was previously planned to be released on 26th of November, but was moved due to Black Week.

erik22 · ‎16-11-2024

Hello i'm wondering the same as @mandem145 is there a way to use the Visma API without the need for user interaction requiring to click the allow button before hitting the callback? We need a way to bypass this somehow!

kashyap · ‎11-11-2024

Getting same issue on many clients. How can we resolve it?

Joni Wolff · ‎27-08-2024

Hi Just wanted to let you know that expand by LOT/Serial is now available in the Sales order API v3 in the GET/Inventory endpoint

thingsio · ‎02-08-2024

Hi, we also have a need to link directly to for example: purchase receipt orders, inventory adjustments etc. Because we pull information from Visma API's in other apps. we also want to link directly from other apps. to make it more convenient for users. For me the second part of the URL is pretty unclear: https://finance.visma.net/1011011001 This number changes once and a while and I don't think it's a version number which can be found in the Swagger documentation. If it can be found in the swagger, to what exactly are you referring in that documentation? A method or something else?

bjornbakke · ‎29-07-2024

Hi, Is this anywhere near now? Since we use multiple curriencies and multiple clients with multiple VAT rates we're really struggling to maintain anything pricewise now.

Sandra Anté · ‎08-07-2024

Hi, Since this is a thread with issues from both the old authentication method and the new method over a couple of years, we recommend that you start a new thread with a description of the current issues you are experiencing. You can also reach out to your local support here: https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710 Kind regards Sandra

Sandra Anté · ‎14-06-2024

Hi again, The fix is turned on for this customer now. We will write and update in the case when it is active in prodcution. Kind regards Sandra

AllanEgebjerg · ‎13-05-2024

@Magnus Johnsen Does this apply for the salesorder /api/v1/salesorder andpoint as well?

Gert-Jan van der Kamp · ‎13-05-2024

Hi we just started having this issue again. We'll wait for it to pass but hopefully you can see something in the logs on why this happens? Client id is isv_xlconnect. Rgds Gert-Jan

Sandra Anté · ‎01-03-2024

Hi, The original cause for the issue posted here should have been resolved. Could you please check the following: "Requested on" date on the header and lines are the same date or earlier than the date you have set for your shipment Also, please try to release it in the UI, it should show you what the issue is. Thank you! Kind regards Sandra Anté

Joni Wolff · ‎29-01-2024

Hi! Just wanted to let you know that this has now been fixed

gordana_jlmwms · ‎18-01-2024

all account have vatcategory id

gordana_jlmwms · ‎18-01-2024

segment value is valid

Magnus Johnsen · ‎18-01-2024

Hi, As far as we have been able to see this also happens in the UI. We would recommend that you get in contact with your partner service regarding this as it's a feature of the system and not a bug in the API.

Magnus Johnsen · ‎17-01-2024

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

Magnus Johnsen · ‎15-01-2024

Hi, Yes that is correct, please let us know if you run in to any issues.

Magnus Johnsen · ‎09-01-2024

That field is the same, however, the county field and some other fields were incorrect which in turn triggered the error incorrectly.

david_magnusson · ‎09-01-2024

This can be closed now, all customers up and running! //David

Magnus Johnsen · ‎17-01-2024

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

JUKKA BLOMQVIST · ‎03-01-2024

It seems to be OK, I think.

Magnus Johnsen · ‎02-01-2024

Hi, We will not shut down your integrations now, we advise you as mentioned to contact your Business Unit if you are not ready. For the issue you receive, could you please list when they are happening and we can bring it up with development. Are there any of those issues that are not related to the initial on-boarding of new clients to the developer portal? Thank you.

jnemo · ‎30-12-2023

Any update? 1st jan closing in

Magnus Johnsen · ‎29-12-2023

Hi, The app needs to be approved, since it's holidays now this might take longer time.

JUKKA BLOMQVIST · ‎28-12-2023

Hello, one more question - managed to add service, but it's in "pending" status for hours - am I still missing some credentials or is this just slow?

Magnus Johnsen · ‎21-12-2023

Hi, Good to hear! Currently it's not possible to use the salesOrder nextGen service for non-stock items. We have an improvement case in the backlog for this, I've informed the developers that you have also requested this feature.

guidol · ‎20-12-2023

Ah, I see. I needed to click save, while all fields were filled correctly, before the Invitation codes box came up.

andreasaulin · ‎19-12-2023

The same again today ... 502 Bad Gateway

Magnus Johnsen · ‎18-12-2023

Call for action to all ISVs and partners having integrations with Visma.net: As you might have noticed we are approaching the deadline (stated in the release notes) for migrating existing integrations from VNI to Connect Authentication. We noticed an increasing activity to migrate in the last couple of weeks but as of today only 20% of the integrations have been migrated to the new authentication. It is therefore very important that you move fast. In case you are not able to migrate before the deadline you should reach out to your Business Unit as soon as possible to discuss your migration timeline. We want to ensure that your integrations won’t stop January 1st. Kind Regards, Visma.net Management

Version 10.29 - Scheduled downtime maintenance win...

Version 10.28 - Breaking change due to mandatory c...

Svar: OAuth 2.0 Authorization Flow

Re: Wrong respons on inventory endpoint with param...

Re: Expose "expand Inventory Summary by Lot/Serial...

Re: Links to documents in VN

Sv: Customer salesprice (ScreenId=AR202000) endpoi...

Re: refresh oauth token

Vastaus: Sub accounts not applied to sales order r...

Re: Inventory Get SortOrder

Re: Error redeeming code: invalid_tenant / no desc...

Svar: Issue posting create shipment on sales order

Re: Salesorder API v3 creating orderLines without ...

Re: TaxID '01' cannot be found in the system.

Re: HIGH priority Subaccount missing, Error creat...

Re: Budget API is not retrieving inactive subaccou...

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

Sv: Getting customer / supplier invoice document (...

Re: Insert supplier

Svar: IPPexception 5520 on every call for select c...

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

Re: Change from test to production

Re: VNI-VC January 1st

Sv: Error: Branch '1 ' cannot be found in the ...

Re: Service app status pending

Re: Cannot access Visma App Store

Re: SalesOrder customer contact v3

Re: invalid_tenant when authenticating using clien...

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

Visma.net statement regarding Connect Authenticati...

Visma Community

Over Visma

Volg Visma