Hi, We're still looking into this, do you happen to have any more examples of truncated errors, if so please send us the ipp-request-id and we'll keep investigating. Thank you.  ... View more

Hi, We are tedting this on our end, when is it you get the issue? Is it when you have created the invoice from the salesOrder? Could you please send us screenshots of the expected results and what happens in your case? ... View more

Hi, We'll test this and get back to you, is there a reason you are using v1 instead of v2?   ... View more

Hi, We're looking in to this and will get back to you.  Are the items with this id set at the same time as your calls, or are they updated after you have updated them through your integration? ... View more

Alright, please do. Thank you.  ... View more

Could you please send us the ipp-request-id and the error message you received? We'll check if it get's truncated on our end.  Thank you.  ... View more

Hi, If we start by looking at one of the companies, could you please try to enter it with the same account in the UI and the API. Could you please make sure for the example above with supplier 25008 that all mandatory accounts are filled in?    ... View more

Hi, You are missing the line operation, the below JSON (modified for use in local company works on our end): { "supplier": { "Value": "50072" }, "type": { "Value": "Payment" }, "paymentRef": { "Value": "Nettan reglering" }, "cashAccount": { "Value": "1963 " }, "paymentMethod": { "Value": "4" }, "paymentAmount": { "Value": 32030.27 }, "applicationDate": { "Value": "2023-06-15T00:00:00.000Z" }, "paymentLines": [{ "operation": "Insert", "refNbr": { "Value": "201945" }, "documentType": { "Value": "Invoice" }, "amountPaid": { "Value": 32030.27 }, "crossRate": { "Value": 7.45446484 } } ] }     ... View more

Hi, It's in the developers backlog, we'll ask them for an ETA.   ... View more

Hi, We can confirm that sending a PUT with accountNumber resets the lines field to the default value of the non-stock item. We'll continue testing and report this to the development team.  Thank you.  ... View more

Hi, Is this in regards to: Visma.Net Financials API endpoint for Employees Please check if editing the employee in the UI triggers an error, send us a screenshot of the screen in the UI. Visma.Net Employee API Please send an email to cloud.api.support@visma.com Thank you. ... View more

Hi, The issue most likely lies with the customer missing some field. We would recommend posting something else to this customer/create a invoice in the UI with this customer to see if there is any errors that are thrown. The lines seem fine but are dependant on the endcustomers settings.  ... View more

Hi, Have you also checked according to the error message: Missing taxable, non-taxable, EU or import accounts. Check the GL account settings for the item, supplier and supplier class  Depending on how each company have set up their accounts in their enviroments results may vary. Have you seen any patterns in what suppliers/items give you errors apart from just the accountNumber?  ... View more

The problem seems to be DNS cache on the Windows Server hosting the App Service. The server most likely has an outdated dns cache. We could not call "ipconfig /flushdns" since the console is not started as administrator user. We have had the same problem with Windows Server VMs in Azure internally in Visma earlier, and flushing dns resolved the issue. ... View more

Hi, Yes the issue seems to be with Azure. We have been looking at this together with Excitec and have managed a temporary solution. We recommend restarting your services/flushing your dns. If we get any more information regarding this we'll post it in this thread. ... View more

Hi, It's been reported to the development team.  The old endpoints are not getting deprecated yet: Move of breaking change Due date for Sales order v1 and v2 Thank you. ... View more

Hi, We'll report this to the development team. Do you have an example of an error message that we can pass along? Thank you.  ... View more

Hi, we'll look into it and get back to you. Could you please send us the full JSON so that we can pass it on to the development team? Thank you ... View more

Hi, For the time being, this is how endpoints that require an user are to be handled:   Hello,  For the moment, the endpoints that are not working with the service API are because of the way the ERP system works. It's designed to pin actions on users, since the service api does not carry any information regarding the user, it's not possible to do for the time being at least. We've registered cases about this with the developers.   Meantime,     there is an option called "offline_access" so that if you need your integration to work after the user has logout of your app, then you can implement the OAuth with offline_access.  Documentation ... View more

Hi, You can find our rate limit policy here: Why am I receiving "HTTP 429 - Too many request / throttling" response from API ? We recommend using the "lastModifiedDateTime" & "lastModifiedDateTimeCondition" to see if any inventoryItems has been modified since your last sync, and then storing/updating a dateTime variable every time you are checking for updates. ... View more

Hi, No, there is no way of increasing the rate limit. We would recommend that you do one initial retrieval to store the translations on your end, and then only update the records that have been changed since your last sync. ... View more

Hi, We have brought this up with the development team and will get back to you when we have more information.  ... View more

Thank you, we'll inform the development team and get back to you as soon as we have more information. ... View more

Then this should work(Do note that the scopes are separeated by a space), in your initial message, the first scope has some punctation in it :      vismanet_erp_service_api:update vismanet_erp_service_api:create vismanet_erp_service_api:read vismanet_erp_service_api:delete     ... View more

Hi, The date that had previously been announced was that the salesOrder v1/v2 were getting deprecated, this is no longer the case, for now, this has been moved to end of Q4 2024. Regarding the authentication methods, currently there is not date set for when the old authentication will be removed, we are no longer onboarding new ISV's to the old method, but it still works just as before.  Regarding your issue, what application type have you registered in the developer portal? ... View more

Hi, We'll raise this with the development team. Thank you.  ... View more

Hi, As far as I know there is no way of getting translations for all inventoryItems. Do you have a particular use case? We might be able to find some infornation that could help you. Thank you.  ... View more

After this action, you'll get a response like this indicating that the process has started: " {     "actionId": "584e8112-6d12-406c-9b6e-ee442809e1aa",     "actionResult": "InProcess" }" After this, what are you doing? Please send us some more details regarding what is done after the creation of the invoice, up until the release action is called and what steps you take after that together with the companyID to developersupport@visma.com and we'll lift it with the development team.  ... View more