About Magnus Johnsen

Magnus Johnsen · ‎16-02-2023

Hi, We'll raise the quiestion internally and get back to you as soon as we have an answer. Thank you!

pjleiwa · ‎15-02-2023

FYI: @Magnus Johnsen: In combination with your answer and openapi2jsonschema, I found what I needed. https://github.com/airbytehq/openapi2jsonschema

Magnus Johnsen · ‎15-02-2023

Hi, We recommend that you get in contact with your partnerService for your market as each market can have different procedures for registering/approving apps/integrations in the store/developerportal. As per my knowledge, all markets require that you complete the certification. Contacting Visma Partner Service / Visma.net ERP Support Thank you.

guidol · ‎10-02-2023

My privileges on the forums seem to be flip flopping, leading to disappearing posts/replies. The Bad Requests seem related due to breaking changes in the swagger. I have created a separate topic on the problems with Swagger (can't find it back but maybe it will appear again). I will try to close this topic.

guidol · ‎10-02-2023

Apologies for the test. My privileges on the forums seem to be flip flopping, leading to disappearing posts/replies. I have created a separate topic on the problems with Swagger, since this one has been marked already as solved.

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 · ‎03-02-2023

Release Notes Documentation Changes on filtering options for paymentType on Customer Payment endpoint Previously, when using API GET Customer Payment endpoint the response message was containing records of types Cash Sale and Cash Return shown as type Payment as well as any other unclassified types. This has now been fixed. The response message contains the same payment types as found in the Customer Payment window (AR302000) and the paymentType filter parameter has a new option "Undefined" for unclassified types Due dates for breaking changes Release Notes. Documentation Due Remove deprecated parameters in Financial Period endpoint The numberToRead and skipRecords parameters for the financial period endpoint are deprecated and will be removed. Feb 28, 2023 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-s... Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

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.

SKAU AS · ‎01-02-2023

I see this issue on one company.

Magnus Johnsen · ‎30-01-2023

Hi, Please do and we'll correct it. Thank you for letting us know.

JoLu · ‎25-01-2023

Hi, Thank you, that sounds like the way to go! Best regards Johan Lundqvist

Magnus Johnsen · ‎25-01-2023

This is planned to be included in the 9.32.0 release [31/1/23]: Previously, the "salesCategories" field in Inventory endpoint returned only sales category description. This has now been changed so that the endpoint will return both the category ID and the category description.

AntonZ · ‎23-01-2023

Hi Magnus! We have another issue also related to interest/fee voucher creation in Visma.NET This time its account specific, as it works fine for one of our customers, but does not work for the other. We suspect its some setting in Visma.NET that isnt active in account that gives error, but we havent been able to figure it out. Here is the error message we get: {"message":"VismaId: f948dfa5-350c-49c7-bdf9-5e40729a2804. Error creating document. Error: TaxCategoryID '0' cannot be found in the system."} Is this what we must do? 1. Check the customers Vat Zone - Get /controller/api/v1/customer/{customerNumber} 2. Get the Vat zones applicable Vat Id's -Get /controller/api/v1/vatZone/{vatZoneId} 3. Get the invoice lines Vat categories applicable Vat Id's -Get /controller/api/v1/vatCategory/{taxCategoryId} 4. The Vat Id needs to be a value found in both lists. - Get /controller/api/v1/vat/{vatId} Can you point us towards where to set up the Visma.NET account so its possible to export to it?

Magnus Johnsen · ‎20-01-2023

Since the integration is registered via the dev portal, you shouldn't use the legacy authorization method. Please have a look at this documentation for the Visma developer portal. If you are still having issues after this, please send us an email at developersupport@visma.com with details regarding what you currently have set up. Please include screenshots from the portal as well. Thank you.

Magnus Johnsen · ‎20-01-2023

Hi Steinar, For the Employee API, you can send your questions to cloud.api.support@visma.com. We have informed them about your questions as well.

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

Hello, this issue has been fixed in [Release Notes] - Visma.Net API 9.30.0 - 17.01.2023

Magnus Johnsen · ‎20-12-2022

Hi, Currently the information supplied via the "supplier/supplierClass" & "supplier/supplierClass/{supplierClassId}" are the only endpoints related to the supplierClasses exposed via the API. We recommend that you create a post in the "Ideas" section of the forum.

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

Hello, have you tried updating/creating with the salesPerson first then sending PUT request for the subaccount ?

Magnus Johnsen · ‎07-12-2022

Hi, The financial details of the customer/supplierInvoice are not exposed as of today. When using the api, the defaults from the supplier or customer are set: If you need this functionality, please create a post in the Ideas part of the forum.

JoLu · ‎07-12-2022

Hi, How about adding these kind of limitations to the API-documentation, we also discovered this by chance and would have found it a bit earlier if it was in the documentation?

Florian Haase · ‎05-12-2022

Hi Magnus what is the status here? We have still the same issue... Florian

Magnus Johnsen · ‎05-12-2022

JohanFriedrichsen · ‎29-11-2022

Any updates on this question? We would like to be able to get the next delivery date as a parameter on the inventory item itself. Would that be possible?

Magnus Johnsen · ‎29-11-2022

Hi, For the action "ExtendToVendor" from the customer screen there is a improvement request in our backlog. It is currently not planned, we have asked the developers for an update and will get back to you when we have received feedback: When it comes to the respective action for the supplier ("ExtendToCustomer") there is currently no improvement request in the backlog. If this is functionality that you wish to be implemented, we recommend that you create a post under the "Ideas" part of the forum, explaining your business need as well as providing as much info regarding the screens from the UI that you would like extended to the API. Thank you.

Magnus Johnsen · ‎28-11-2022

Hi, As mentioned in the post, if you're missing the license in your company and need help regarding ERP related topics you should contact your Partner Service from your market. When you have been able to activate the license, you can find the project on ScreenId=PM3010PL: And the project tasks at ScreenId=PM3020PL: For more guidance regarding the ERP UI, please refer to your partner service. Thank you.

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.

Magnus Johnsen · ‎23-11-2022

Hi, This case is currently not in any plans. We have asked the team for more details.

Dante Cavallin · ‎17-11-2022

Yes it is the same user.

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

Hello, the Cash Account ID "6891" shown in the error message is the Account ID of the cash account you've used in the payload "cashAccount": { "Value": "0123" }, This can be found at Chart of accounts(ScreenId=GL202500) When it comes to the error, apparently you don't have access to that account via the "branch": { "Value": "23" }, In order to be able to Create a Customer Payment with specific PaymentMethod and Cash Account, Cash Account/s that you'd like to use with "CustomerPaymentMethod" should be defined under the Payment methods:"Allowed Cash Accounts" in Financials ERP ScreenId=CA204000 regardless of what branch is in use. then this cash account can be selected when creating a customerPaymentMethod. Regarding having multiple branches in your company and if those accounts are defined as branch-specific, Please make sure that "Multi-branch" and "Inter-branch transactions" are active in your licence and enabled in the Financials ERP company. Afterward, go to desired "Cash Account" screenID:CA2020PL and set "restrict visibility with branch : false"

Gert-Jan van der Kamp · ‎09-11-2022

Hi apologies for the late reply, I couldn't post to the forum. I setup an app registration isv_xlconnect in the developer portal, it's Native app with PKCE and OpenID Connect. Then use this code with IdentityModel to get the cookie: var options = new OidcClientOptions() { Authority = "https://connect.visma.com", ClientId = "isv_xlconnect", Scope = "openid email profile offline_access", RedirectUri = "http://localhost:8888/callback/" }; That all works fine, it returns a webtoken. But the call to the api abobe fail with the message. One thing I can see is that the applictation regsitration I made in the dev portal uses as https://connect.visma.com authority, while the api uses https://signin.visma.net/ when I click authorize on the Swagger Docs. Could that be the issue?

Re: Removal of salesorder endpoints June 1st

Re: How to retreive column definition of an endpoi...

Re: current policy on API access for customers

Re: HTTP 400 Bad Request answers

Re: Visma.Net API Swagger page not showing

Svar: Visma.Net updated today?

[Release Notes] - Visma.Net API 9.32.0 - 02.02.202...

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

Re: Webhoook resourceURi

Re: "error": "invalid_scope"

Re: Visma Connect Authentication for Visma.net ERP...

Re: Get inventory - salesCategories show descripti...

Re: Setting status of CustomerInvoice when creatin...

Vastaus: Authorization GET request fails

Sv: GET http://employeeapi.employeecore.hrm.visma....

Re: Missing "Description" field on SupplierPayment...

Re: Fetch and create supplier classes

Re: subaccounts salesorder lines

Re: Is it possible to input dimensions to the cust...

Re: Inconsistency when fetching supplier invoices

Re: Empty VATCode on CashtransactionLine

Re: SupplierPayment in a specific branch - Status ...

Re: Best practice for finding next deliverydate fo...

Re: ExtendToCustomer/ExtendToVendor

Re: How can I access project and project task from...

Re: Sales Order Api questions

Sv: Missing exchangerate in Customer Creditnote?

Re: Issue when addning subaccount on Customer invo...

Re: Create customerPayment error

Re: 401 Unauthorized: Invalid audience when callin...

Useful pages

About Visma

Contact us

Follow us