About Magnus Johnsen

Magnus Johnsen · ‎12-12-2023

A fix for this issue has been deployed and been confirmed to solve the issue. If it arises again, please let us know. Thank you.

Magnus Johnsen · ‎12-12-2023

Hi, The role needed to log in to an interactive integration is the "API User" role, the "Integration Administrator" is only needed for the users that should have access to log on to the App store and accept tenant based applications. Could you please check if this has been applied to one of the users logging in:

Magnus Johnsen · ‎11-12-2023

Hi, Does the user you are logged in with have the "Customer Administrator" role? If so, they should be able to assign the "Integration Administrator" to any other user in that company.

Magnus Johnsen · ‎08-12-2023

Hi, According to the documentation, openID is required as scope. Using email and/or profile as well gives you the possibility to also get information about the user via the UserInfo endpoint. Example: curl --request GET --url https://connect.visma.com/connect/userinfo --header 'authorization: Bearer [YOUR_ACCESS_TOKEN]' Response: { "sub": "1072cd43-d99a-4d44-84a2-5f80720c1a19", "name": "John Doe", "given_name": "John", "family_name": "Doe", "email": "john.doe@visma.com", "email_verified": true, "idp": "Visma Connect", "auth_time": "1472622102", "sid": "11474d36-22a3-40d8-925d-21af17826e38" }

Magnus Johnsen · ‎08-12-2023

Hi, When it comes to the App store, native apps use the interactive authentication and does not need to be published as "invite only" as the API-scopes are based on the roles the user that authenticates has on it's account. You can still choose to add marketplaces if you want your application to be visible on the Visma App store. Regarding the redirect_uri, Visma Connect does not support dynamic/ephemeral port for the redirect_uri's. One option is to register multiple redirect_uri's with different ports and choose the one that is available at runtime, another perhaps better option would be using a custom URI scheme and configure Windows to open the app when it is invoked, similiar to how Slack works with their desktop app. Please let us know if you have any other questions and we'll raise it internally. Thank you.

Magnus Johnsen · ‎08-12-2023

We have merged these two threads. We have deployed a fix for the issue and are still monitoring it, the status of the incident can be followed here: https://status.visma.com/ Please let us know if you are still having issues.

Magnus Johnsen · ‎08-12-2023

We are planning to have two Maintenance windows next week: 1. Monday 11th of December 16:00 - 19:00 CET Maintenance on Demo and Template companies to improve performance. These companies will be unavailable, all other functionality will work as usual. https://status.visma.com/incidents/41dclr3f8kh3 2. Tuesday-Wednesday night 13th of December 01:00 - 04:30 CET. SQL infrastructure optimization. This is continuity for the Azure migration and was decided to do after migration weekend. Visma.net ERP UI and API will be unavailable during the maintenance window. https://status.visma.com/incidents/1qkwfgjk2y0h

Magnus Johnsen · ‎06-12-2023

Hi, The "Invite only", it can be found here: Regarding the redirect_URI, we'll check this internally and get back to you.

Magnus Johnsen · ‎01-12-2023

Hi, As this is not currently implemented we have moved the post to the Ideas part of the forum. The current possibility here is to use this endpoint to get the customer data: /controller/api/v1/customer/internal/{internalID} Thank you

Magnus Johnsen · ‎30-11-2023

Hi, Is this demo company newly created? We are not able to reproduce the issue using the same JSON, could you please try again? Thank you.

Magnus Johnsen · ‎30-11-2023

Hi, This issue should now have been resolved, please let us know if you're still having issues.

Magnus Johnsen · ‎30-11-2023

Hi, Could you please have a look at this thread and let us know if it helped solve the issue: 'Access denied' during authorisation through Visma Connect Thank you.

Magnus Johnsen · ‎30-11-2023

Hi, Please send us an email at developersupport@visma.com with an example of a JSON that fails, the companyID and name. We'll forward this to the development team. For now the only known workaround has been retrying the operation at a later point.

Magnus Johnsen · ‎30-11-2023

Hi, We are currently investigating the issue, you can follow the status here: https://status.visma.com/incidents/1ct771l24zhz

Magnus Johnsen · ‎29-11-2023

Hi, Please make sure that the user you are using has the roles "Financials Administrator" & "Financials User": Note: The "API user" role here is only needed for the interactiv authentication via the developer portal. Please let us know if you still have these issues when the roles have been applied in Visma Admin.

Magnus Johnsen · ‎23-11-2023

Hi, We recommend trying to recreate the same invoice in the UI manually, to see if there any warnings/errors that are triggered. If none, please send the JSON you are trying to post and we'll try to recreate it on our end.

Magnus Johnsen · ‎23-11-2023

Hi, It refers to these fields in ScreenId=AR303000: Check this customer in the UI, and make sure that the Locations subaccounts are set to an existing subaccount combination. Or update the location via the location endpoint. Please let us know if you still have issues after this. Thank you.

Magnus Johnsen · ‎22-11-2023

You're welcome 😀

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.

Magnus Johnsen · ‎20-11-2023

Hi, Are these the fields that you are refering to? "defaultWarehouse": { "value": "string" }, "defaultIssueFrom": { "value": "string" }, "defaultReceiptTo": { "value": "string" },

Magnus Johnsen · ‎17-11-2023

Hi! The development team has found a solution that is planned to be released 21/11, version 9.71

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

Magnus Johnsen · ‎16-11-2023

The link has been updated: https://community.visma.com/t5/Knowledge-base-in-Developers/xxx-of-SubAccount-can-t-be-found/ta-p/272417

Magnus Johnsen · ‎16-11-2023

Please have a look at this article: “xxx” of SubAccount can’t be found

Magnus Johnsen · ‎15-11-2023

Hi, You are missing the operation on the invoiceLine: "operation": "Insert", Please include it in your payload and try again. Thank you.

Magnus Johnsen · ‎15-11-2023

Hi, The due date for the removal of the old fields can be found in the release notes: [Release Notes] - Visma.Net API 9.70.0 - 14.11.2023

Magnus Johnsen · ‎10-11-2023

Thread continued in: https://community.visma.com/t5/Forum-in-Developers-Visma-net/List-all-item-attributes-defined-for-a-customer/m-p/618136

Magnus Johnsen · ‎10-11-2023

Hi, These fields will only be populated when the invoices have been created via the sales module, or from a salesOrder. The customer invoices are split up in two modules: 1. Customer ledger 2. Sales Via the Get all CustomerInvoice you'll get a collected pool from both sources, some fields are specific to the sales module, like "lineType". Posting customerInvoice, only allows you to create an invoice in the Customer Ledger module.

Magnus Johnsen · ‎10-11-2023

Hi, To get all attributes you can use the Attribute endpoint: This will include attributes that might be used for inventory, to get what item's has what attributes you use the parameter "expandAttribute" and set it to true: /controller/api/v1/inventory?expandAttribute=true

Magnus Johnsen · ‎09-11-2023

There is a scheduled maintenance window the 12th of Octover 01:00-05:00, during which both the Visma.net ERP and API will be unavailable. We are improving our scalability to be better prepared to handle extreme work loads, we also hope to resolve the Gateway issues that we have been seeing. You can follow the status here: https://status.visma.com/incidents/zngd6yr9ljy6

Re: Action confirmShipment fails

Re: Can't assign App Store “Integration Administra...

Re: Can't assign App Store “Integration Administra...

Re: Question on native app authentication

Re: Question on native app authentication

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

Visma.Net Scheduled Maintenance - 11th of December...

Re: Question on native app authentication

Re: CustomerNumber in SalesPerson Endpoint - Statu...

Svar: SQL error when creating journal transactions

Re: https://integration.visma.net/API/controller/a...

Re: Access denied

Re: Felmeddelande med inläsning av filer via API

Re: https://integration.visma.net/API/controller/a...

Re: API account roles have been changed suddenly -...

Re: Error creating a document.

Re: PUT api/v1/customer/#{debtor_nr}"

Re: Expand inventory endpoint with standard locati...

Re: create a customer invoice from a shipment?

Re: Expand inventory endpoint with standard locati...

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

Re: critical error posting orders to salesorder ap...

Re: POST customerInvoice ERROR: Operation paramete...

Re: POST customerInvoice ERROR: Operation paramete...

Re: POST customerInvoice ERROR: Operation paramete...

Svar: Problem with Visma.net API - missing externa...

Re: List all item attributes defined for a custome...

Re: Attributes missing CustomerInvoice

Re: List all item attributes defined for a custome...

Visma.Net Scheduled Maintenance - 12th October 01:...

Useful pages

About Visma

Contact us

Follow us