Hi! Questions regarding Visma.net integrations/API can be posted in the forum of the developers community. Could you ask your questions there? https://community.visma.com/t5/Forum-in-Developers-Visma-net/bd-p/DV_CO_Vismanet_forum Thanks in advance. ... View more

Hi! We have no known disruption of the service, I have just checked and the site responds normally. Could you have another try? ... View more

Hi Jukka,  Is the option client credentials enabled in your app? Do you have linked the tenant to the app by inserting the invite code? It should be visible under Customers:   ... View more

Thx for the update Sander! ... View more

Hi Mathijs, the refresh token lifetime is always based on initial codeflow. It determines how long you can use the app without having to log in again. One time use is only an additional layer of security. If every new refresh token would have its own expiration time, then you would effectively have an unlimited use in combination with the setting but will expire if not used in.    You will find other examples of this practice, for example https://developer.okta.com/docs/guides/refresh-tokens/main/#:~:text=Note%3A%20When,user%20first%20authenticates.   Let us know if this answers your question. ... View more

Hi! A credit write-off is an internal document used to write-off a credit note. It can only exist when applied to a credit note and cannot be printed as a document. Therefore from an API request you will not receive an address in the response. In UI it is only there because it is opened from the invoice screen with standard layout.   In the endpoint documentation the expandInvoiceAddress is there because this is part of the standard customerdocument, just like there is dunningLetterDateTime for example. These fields serve no purpose for this type of document.   Can you elaborate why you would need an address from this documenttype? ... View more

Sorry, you have to be a certified ISV partner to be able to create cases. You can send an e-mail to cloud.api.support@visma.com. ... View more

Hi, this parameter is not implemented in the endpoint yet. You are welcome to create a post for this in the Ideas section of this forum. Thanks in advance! ... View more

Yes you are right, there has been a change in the way we support API, now we can provide more specific support if this is needed. You are welcome to create a case for Norway https://visma-swno.my.site.com/s/api.   ... View more

Thank you for the information Roland! We have had contact in our support portal and have made a case for this. ... View more

Hi! Thank you for the information, I have checked several log entries, and found the error messages. The logs unfortunately do not tell us why the message occurs, because in this case it will be a combination of masterdata and configuration.   As you have checked all possible settings, I advice you to seek country-specific support. There we can investigate more in depth what the underlying cause is. Please check https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/td-p/633804  on how to contact us. ... View more

Hi Joel, unfortunately there is no event in place for deletion. It might be an interesting idea to post in the ideas section; https://community.visma.com/t5/Ideas-in-Developers-Visma-net/idb-p/DV_CO_Vismanet_ideas ... View more

Hi, yes that is the correct URL, thanks for the update! ... View more

Thanks for the information, I have tested these and confirmed this behavior. Unfortunately credit control has not been implemented through API. This functionality uses logic in the web interface that is not yet available for API.   I understand this wish is taken into consideration for future releases, but there is no timeframe or confirmation for it yet. Hopefully you can find alternative methods for this. ... View more

Hi Gert-Jan, glad it works now! Yes the PK also contains the lineNbr, together with the stockitem and revisionID. This can be a bit trial and error sometimes, but the provided example in https://integration.visma.net/API-index/ should always work or give a meaningful error message.  ... View more

Hi Gert-Jan, can you describe how you have deleted the incorrect items? Are you able to add any kitspecifications at all? If not can you try to upload a different revision?   ... View more

Hi! This forum is specifically for questions regarding API development, i advice you to ask this question at your country specific community or support for Visma.net ERP. Contacting Visma Partner Service / Visma.net ERP Support ... View more

Hi Kanyar, which endpoint do you use for salesorders? Thx in advance for your information! ... View more

Hi Tapiiros, unfortunately system tables are not directly accessible by API. All available information is registered here: https://integration.visma.net/API-index/ Alternatively you can seek assistance from your local partner with Visma.net ERP knowledge to help you in this process.  ... View more

Thanks for the information! I have tested this with the same settings and your supplied script. I was not able to reproduce this behaviour, in my test both api and UI provide the same costprice based on the components. Further investigation is needed. I advice you to contact country specific support, because this seems to be specific for your situation. For more information see https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710 ... View more

Hi,    I see from your screenshots it is a non-stock kit item. So the costprice will come from sub items, which will be calculated when releasing the salesinvoice. Hence, normal behavior for the non-stock kit item on entry would be to show  a costprice of 0, unless you enable the setting Kit cost based on components Sales order preferences. If you enable this you directly see the total cost of all components.   The reason why you see a costprice when entered in UI is probably because there has been a purchase or receipt transaction with this price earlier, can this be the case?   ... View more

The only way I can reproduce this error if I leave the body completely empty. I suspect there is something wrong with the url encoding or form structure of the body. If this does not help you, I suggest you take this up with local support, because we need to do an in-depth check on what is the cause of this error. You can find local support on this page: https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710 ... View more

Can you check if the users have api-user rights? This can be configured in Visma.net admin. See also https://community.visma.com/t5/Forum-in-Developers-Visma-net/VISMA-net-shows-error-page-during-OAuth-flow/m-p/616587 ... View more

Hi Erik, I see you have a username in the request, this should not be needed. Furthermore, some fields seem to be missing in the body of your token request. It should be like this Curl example request:   curl --request POST --url https://connect.visma.com/connect/token --header 'content-type: application/x-www-form-urlencoded' --data 'grant_type=authorization_code&redirect_uri=https%3A%2F%2Fdemoapp.example.com/oauthcallback%2Fcallback&code=94c99b73c13c1e39f7b0a7d259628338&client_id=demoapp&client_secret=SECRET'   Let me know if this helps you. ... View more

Ok, you should have rights now. Could you try again? ... View more