Hi, As far as I can remember I have not come across this before, we recommend getting in contact with the ERP support team for your market.  Contacting Visma Partner Service / Visma.net ERP Support ... View more

Visma.Net API does not support CORS, i.e. you can't call it from a browser. in short, the browser only allows requests to API:s on the same domain as the page was fetched from unless the API explicitly allows it (CORS). This is a browser security feature   There was a request for enabling CORS in the API many years ago but it was denied. I assume the reason is the API authentication uses a non-expiring token which can not be securely stored in the browser. Haven't looked into it but with the new authentication (OAUTH) it might be possible to use the API without storing keys in the browser so the decision could be reevaluated.   ... View more

Hi, These fields are currently not available in any of the salesOrder endpoints. If this is functionality you need, please create a post in the "Ideas" part of the forum. Thank you.  ... View more

From screenId  GL202500, and now create customer invoice successfully ... View more

Hello, you can find additional information about the fix and the background of the case below.    1) https://community.visma.com/t5/Forum-in-Developers-Visma-net/Sales-orders-V3-created-by-id/m-p/584084#M3699 2) POST Sales Order Service API - "createdById" and "lastModifiedById" set with API_Client_ID [Release Notes] - Sales Order Service API 1.0.14.648 ... View more

I can confirm, this was an implementation issue on our side. The Visma.net API works correctly as Magnus reported above. ... View more

Hi, The only payment method that is returned using the supplier endpoint is the one set under the suppliers "payment settings". The supplierLocation endpoint does not return this information either. If this is functionality that you need, we would recommend that you create a post in the "Ideas" part of the forum.  Setting the correct paymentMethod on each location should allow you to not have to specify what payment method you want to use. ... View more

Hi, This was marked as fixed for v9.12. Are you still having issues with this? ... View more

Hi,   Any news on this issue? ... View more

Never mind, I'll delete the clip itself on loom ... View more

Correction: the problem occurs with SalesOrder but not with SalesOrderv2   It is the contacts that are affected. If "overrideContact" = false is combined with additional values (see below) on the first SO for a customer these values will be used on this SO and every consecutive SO, regardless of if it is created via API or manually.    "soBillingContact": { "value": { "overrideContact": { "value": false }, "name": { "value": "Billing Contact" }, "attention": {}, "email": { "value": "billing.contact@mail.com" }, "phone1": {}, "phone2": {}, "fax": {} } },   It can be argued that override and extra values shouldn't be used at the same time but there is nothing stopping it (tehcnically or in the docs). The effects are also very problematic since it will affect every future SO.   Regarding the use of v1 over v2: we had prior to this no urgent reason to move to v2 since the focus was on the initial SalesOrderService timeline. But since that has been pushed we have to rethink what we need to do. ... View more

Hi, We would recommend that you create a post in the Ideas part of the forum if this is functionality that you wish to have available. We don't have a exact reason this whas not implemented in the first version, the API does not cover all functionality of the UI. ... View more

Hi, you have InternalID and ProjectID in your PUT (Update) payload, you should only include the fields in the payload that you'd like to update.  ... View more

Ok, could you please send the company-id's where you have this issue as well as salesOrderNumbers to developersupport@visma.com and we'll forward this to the development team for investigation. Thank you.  ... View more

i Got it working my local cashe where playing a trick on me Ctrl+Shift+R got it working. have u seem my question regarding findings in regards to warehouse and toWarehouse filtes ?  it seems like toWarehouse filter only works if used WITH warehouse and not alone  is this intended ?  ... View more

Alright, please do. 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

Thanks! I tried linking the customer to a new invoice directly in the UI and received a more detailed error regarding an invalid zip code. It would be greatly appreciated if in the future you could get this error message out rather than the current "Object reference not set to an instance of an object.".   It would have made it a lot easier for us in troubleshooting. ... View more

Fantastic - you are right. Switching the App-Serviceplans fixed the problem. Thank you for helping! ... 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

Note: I found another issue relating to this endpoint. Might be efficient for the developers to look at them together: https://community.visma.com/t5/Forum-in-Developers-Visma-net/The-PUT-operation-on-a-Customer-to-add-a-DirectDebitLine-does/m-p/583316#M3674 ... 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