About SierdW

Marten Voort · ‎08-10-2024

Not yet Sierd, I will investigate and come back to you.

SierdW · ‎08-10-2024

The relativeResourceUri and resourceUri are incorrect, the CRM part should be removed frorm the uri. We had a similar question but it has not been fixed yet, apparently: https://community.visma.com/t5/Forum-in-Developers-Visma-net/arinvoice-changed-webhook-creditnote-and-debitnote-wrong/m-p/665233

Marten Voort · ‎04-09-2024

I have just done some testing, for the entity customers there is no noticeable delay, so there is no need to add a delay for this.

SierdW · ‎17-04-2024

Hi Suzdar, Thanks for the update. Sierd

Yıldırım · ‎16-12-2023

Hello, we got confirmation from Ali that it's working now. You can contact us if this occurs again. Thanks.

Magnus Johnsen · ‎30-11-2023

Hi, Could you please have a look at this thread and let us know if it helped solve the issue: 'Access denied' during authorisation through Visma Connect Thank you.

ReinderReinders · ‎31-10-2023

I have just run into this issue as well. My functional Tester tells me that she has observed that even though we do not pass a Branch ID on a DirectDebitLine (because there is no field for it), the DirectDebitLine is automatically linked to the first Branch recorded for a Company. This is undesirable (it should be left empty, so available for all Branches - the same way the UI works). Can a status be given for this issue and when it will be resolved?

Yıldırım · ‎12-10-2023

Hello again, we've got confirmation that the authorization/access tokens are not going to be affected by the migration.

Magnus Johnsen · ‎23-02-2023

Hi, Currently, we have only stated that we want to start removing the old authentication method in Q3/4. There is no set date at the moment, as soon as we have a date or more information we will post the information on the forum. In regards to the notificaition period, the post mentioning the new method and our wish to move away from the current solution was posted the 7th of December. As per our policy regarding breaking changes we strive to inform all ISV's via the forum at least three months prior to the change. Generally this period is longer, you can read more about this here: Notifications regarding breaking changes in the Production environment The NextGen SalesOrder API was in a different position when it was announced and still is. It was made available early with only a few endpoints to allow for the community to be involved in shaping the functionality of the new service.

SierdW · ‎30-01-2023

Update from my side: it works now, I made the following modifications: My lines array was incorrect formatted I missed the branch on the line I missed the operation on the line I missed the date on the line I missed the financialperiod on the line The following message was succesfully posted: { "description": { "value": "test" }, "lines": [{ "operation": "Insert", "branch":{"value":"10"}, "project": { "value": "23.22639" }, "projectTask": { "value": "SA" }, "accountGroup": { "value": "501" }, "date":{"value": "2023-01-15"}, "financialPeriod":{"value": "202301"} } ] }

Magnus Johnsen · ‎11-10-2022

Hi, This should not be an issue for anyone, this is only regarding the Swagger UI. When testing the API we recommend using a client like Postman/Fiddler or cURL with your own token. By doing this, you will not encounter this rate limit.

SierdW · ‎28-06-2022

Hi Magnus, I wasn't aware of the fact that availabilityLastModifiedDateTime was filtering on modified stock quantities, thanks for bringing it to my attention. I will consider using the neXtGen service! Thanks, Sierd

Yıldırım · ‎31-05-2022

Hello Sierd, the API is processing the operations as the user being logged in via the main branch, and it seems, omitting the branch value sent in the payload so not allowing cash accounts restricted to different branches. Have you tried the same operation via POST Salesorder V2 ? Please also send us your ipp-company-ID <developersupport@visma.com> Thanks.

Magnus Johnsen · ‎27-04-2022

Hi, Please send us the results from the query to developersupport@visma.com and we'll have a look at it and raise it with the development team. Thank you.

SierdW · ‎21-03-2022

On /controller/api/v1/customer we can assign a parent Customer: "parentRecordNumber": { "value": "string" }, But for consolidating open items we need to set the interface checkbox ConsolidateToParent. It seems this is not exposed in the API, is this correct and if so, will this be enabled in the near future?

SierdW · ‎22-10-2021

For a customer specific integration we want to set the TaxZone on a SaleOrder. The TaxZone is available (I assume) as customerVATZone, but I'm missing the boolean property to override the taxzone: Can this OverrideTaxZone property be added to the saleOrderUpdateDto so that we can set it?

Yıldırım · ‎02-08-2021

Hello, establishing a new Endpoint for "Fixed Assets" Module {POST/PUT/GET} - (ScreenIDs FA303000 / FA301000 / FA3010PL) is in our backlog. Development plan hasn't been emerged, yet, therefore we're unable to share implementation date at the moment. We'll keep the idea update on any progress.

Re: arinvoice_changed webhook creditnote and debit...

Re: Webhook with possible wrong URI

Re: Delay between Visma Net API and Sales Order Ap...

Re: Customerpayments query filtering limitations

Re: Error 5520 on every call

Re: Access denied

Re: Customer DirectDebitLines: set brancheId

Re: Migration to azure: Will tokens persist?

Re: End old authentication method September 2023?

Re: Error creating project transaction document

Re: Pagination and SameRequestLimit

Re: Retrieving changed stock quantities

Re: Cash account 'id' cannot found in the system

Re: Incorrect metadata totalcount in SupplierInvoi...

ConsolidateToParent on Customer endpoint

Missing SaleOrder OverrideTaxZone in Api

Re: Add fixed assets endpoint - Status changed to:...

Useful pages

About Visma

Contact us

Follow us