About mrtnsn

Roland van Belle - Consolit · ‎14-04-2022

We now have a very urgent case for this functionality. Unfortunately we have to work with custom importdefinitions, insteat of the modern API connection. Please give us an update about this case. We really urgently waiting for this function in the API (put/delete customerprices). Thank you for the update!

AliMKhan · ‎16-11-2021

Hello. Sorry for the late reply. 1) As mentioned earlier by Roy, we are working on improving our endpoints, so they can respond faster and deliver more specific information instead of everything as of now. One example of this work is the neXtGen SalesOrderService which includes v3/salesorder, v3/inventory and v3/customer More info about it can be found here: Getting started with the first neXtGen service: Visma.net ERP Sales Order API 2) As you are mentioning, we are running in a multi tenant environment with shared resources, and we have to have in place some measurements to ensure the quality of the service. That is the reasoning behind having a concurrency policy. We have not landed on a number yet, but it will most likely be a percentage of the resources available in the environment.

Magnus Johnsen · ‎06-11-2020

Are you receiving the ipp-request-id in the response header? Please also make sure that your user has both "Financials Administrator" & "Financials User" roles assigned for this company. And please try to open a location in the UI to see if you can access it there. If so, please send us your API client ID, ipp-company-id and the request-id to developersupport@visma.com and we'll have a look. Thank you.

mrtnsn · ‎26-10-2020

It worked via Postman so I will investigate what is happening when setting a field to true from the code.

Magnus Johnsen · ‎09-10-2020

Ok, please let us know if we can do anything else.

Pierre Reklev · ‎09-10-2020

Hei Kan du være så vennlig og sende oss en forespørsel på dette på contractingsupport@visma.com hvis du ikke har fått hjelp med dette allerede? Jeg klarer ikke å opprette en sak direkte da jeg ikke ser hvilket firma du representerer. 😃 Tusen takk

Yıldırım · ‎08-10-2020

Please do that, then we can check this out with the team if this can be implemented. Thanks !

mrtnsn · ‎08-10-2020

It should be possible to DELETE an customer via the API. This is possible through the GUI and the endpoint should replicate the behaviour of that action. The response should contain good error messages for when an customer cannot be deleted.

Magnus Johnsen · ‎25-09-2020

Hi, The best way to find out this information apart from getting the document via the API and looking at the fields is to check Swagger. What ScreenID corresponds to what endpoint van be seen in the header: For what the fields are corresponding to, you can check the description of the model:

Yıldırım · ‎24-09-2020

Thank you too for bringing this issue to our attention. @mrtnsn wrote: Based on the documentation "This method requires a sales order update dto where the order type is initialised.", so that will still be true I guess. Or if it will be changed to use the same DTO schema as CancelSalesOrderActionDto only requiring "orderType" to be set. I've just updated my post to avoid any confusion, base minimum required DTO schema should be { "saleOrderUpdateDto": { "orderType": { "value": "ORDERTYPE" } } unless user wants to update another field/s in particular. ------------------------- Update: Fix has been planned to be deployed in 8.26 release. Please follow Visma.net Financials API updates for version 8.26 (November) Update: [Release Notes] - Visma.Net API 8.26 - 09.11.2020

Re: Create/Update CustomerSalesPrice

Sv: New throttling policy is in the planning stage...

Re: Where is the Customer EDI Code in API?

Re: CustomerUpdate issues

Re: Placing POReceipts on SupplierInvoice

Sv: Timekost ikke med i DG på serviceordre

Re: Customer DELETE endpoint

Customer DELETE endpoint

Re: Finding correct UI fields in JSON

Re: reopenSalesOrder: Document not found

Useful pages

About Visma

Contact us

Follow us