Over AliMKhan

AliMKhan · ‎24-05-2024

Hello. As mentioned many times earlier, VNI authentication method will have its End of life on 1st of June 2024. This is an urgent notice for all ISVs and partners with integrations in Visma.net: We have previously informed all partners and ISVs to migrate their existing integrations to Visma.net using the new authentication method through Connect. As the June 1st deadline approaches, we still detect traffic from integrations that have not migrated to the new authentication method. Important to know that starting from the deadline, we will initiate throttling of these integrations. This means that we will start limiting the number of calls per hour per integration. During June we will gradually decrease the limit and allow less calls per hour. Additionally, starting mid-June, we will cease to issue new access tokens for these integrations. Please ensure your customers are making the necessary transitions in time.

andreasaulin · ‎30-10-2023

I've sent a few examples to developersupport now

AliMKhan · ‎16-10-2023

Pro tip for ISVs: Subscribe to webhook notification from status.visma.com so that you can automate your integration. Here is how to do it: https://community.visma.com/t5/Knowledge-base-in-Developers/How-to-subscribe-to-the-Webhook-notifications-for-Visma-Cloud/ta-p/346725

JacobIpsen · ‎29-06-2023

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 ?

KonsultVn · ‎31-03-2023

The problem is back since about 15 minutes ago... Can you look into it as soon as possible?

AliMKhan · ‎17-03-2023

The issue seems to have been on one of the IIS server that was handling API calls. For some reason it was not able to connect to the cache, whilst other servers were able to connect at the same time. We suspect that there were too many connections open on that server for some reason. At the moment everything is looking normal and we will monitor the status closely. Sorry for the inconvenience.

AliMKhan · ‎06-04-2022

Due to an error found in the improvement of Inventory endpoint, we have to disable the feature which was to be introduced in 8.91. This means: - Performance improvement is not in effect - Enforcement of pagesize of 5000 is not in effect. We are working on a patch for this, and further information will be communicated when available. We apologize for the inconvenience. ----------------------------------------------------------------------------------------------------------------------------------- Update: The issue has been fixed [Release Notes] - Visma.Net API 8.91.1- 07.04.2022

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.

AliMKhan · ‎19-10-2021

This week, for the first time in a long time, we will have some down time when upgrading to the next version. More info here: https://status.visma.com/incidents/n6tg21tg8bnl

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

Hello Véronique, Yes, that is correct. This is specified in the article: Why am I receiving "HTTP 429 - Too many request / throttling" response from API ? "Applies to" column in the throttling configuration table. Please also have a look at Visma.Net Integrations Startup Guide > Background Information on API Client & Token & Visma.net Financials User & Company section to have better overview about the API Client & Financials ERP Company association logic.

Yıldırım · ‎25-11-2020

Update: The issue has been addressed. This was related to DNS, the issue has been occurred between our proxy servers and endpoint's environment. The problem should now be resolved. Postmortem will be provided at the status.visma.com We are sorry for the standstill this may have caused in your integrations. Please let us know whether you are still facing the problem.

Yıldırım · ‎19-11-2020

@christianth It's great to hear that is serving its purpose, thanks for the feedback.

Anonymous · ‎10-11-2020

I logged all the webhook-messages that was sent during the upgrade to 8.26. In total 8 notifications was sent: 21:31 - Incident update - Scheduled maintenance for Visma.net ERP 22.30 - Component update - Visma.net ERP API - Under maintenance 22.30 - Component update - Visma.net ERP - Under maintenance 22.30 - Incident update - Visma.net ERP API - Maintenance in progress 22.55 - Incident update - Visma.net ERP API - Still under maintenance 01.35 - Component update - Visma.net ERP - Operational 01.35 - Component update - Visma.net ERP API - Operational 01.35 - Incident update - Visma.net ERP - Completed An example of the Incident update: { "meta": { "unsubscribe": "http://status.visma.com/?unsubscribe=9j1hhlv61p90", "documentation": "https://help.statuspage.io/knowledge_base/topics/webhook-notifications", "generated_at": "2020-11-09T20:31:24.480Z" }, "page": { "id": "zvpknzcr6znl", "status_indicator": "none", "status_description": "All Systems Operational" }, "incident": { "name": "Scheduled maintenance for Visma.net ERP", "status": "scheduled", "created_at": "2020-11-06T16:49:26.024+01:00", "updated_at": "2020-11-09T21:30:30.935+01:00", "monitoring_at": null, "resolved_at": null, "impact": "maintenance", "shortlink": "https://stspg.io/dvqy02dtggw5", "scheduled_for": "2020-11-09T22:30:00.000+01:00", "scheduled_until": "2020-11-10T05:30:00.000+01:00", "scheduled_remind_prior": true, "scheduled_reminded_at": "2020-11-09T21:30:30.935+01:00", "impact_override": null, "scheduled_auto_in_progress": true, "scheduled_auto_completed": true, "metadata": {}, "started_at": "2020-11-06T16:49:26.016+01:00", "id": "67kvyh0xn9xh", "page_id": "zvpknzcr6znl", "incident_updates": [ { "status": "scheduled", "body": "Maintenance will begin as scheduled in 60 minutes.", "created_at": "2020-11-09T21:30:30.246+01:00", "wants_twitter_update": false, "twitter_updated_at": null, "updated_at": "2020-11-09T21:30:30.246+01:00", "display_at": "2020-11-09T21:30:30.246+01:00", "deliver_notifications": true, "tweet_id": null, "id": "bd4ppzq438c6", "incident_id": "67kvyh0xn9xh", "custom_tweet": null, "affected_components": null }, { "status": "scheduled", "body": "We will be undergoing scheduled maintenance from Monday, November 9th, 22:30 CEST until Tuesday, November 10th, 05:30 CEST. The version 8.25.49.1020 will be upgraded to 8.26.08.1036.", "created_at": "2020-11-06T16:49:26.074+01:00", "wants_twitter_update": false, "twitter_updated_at": null, "updated_at": "2020-11-06T16:49:26.074+01:00", "display_at": "2020-11-06T16:49:26.074+01:00", "deliver_notifications": true, "tweet_id": null, "id": "30tpfrxjcn11", "incident_id": "67kvyh0xn9xh", "custom_tweet": null, "affected_components": [ { "code": "3hbtn55fszt8", "name": "Visma.net ERP - Visma.net ERP", "old_status": "operational", "new_status": "operational" }, { "code": "k6jrxjnvv3zt", "name": "Visma.net ERP - Visma.net ERP API", "old_status": "operational", "new_status": "operational" } ] } ], "postmortem_body": null, "postmortem_body_last_updated_at": null, "postmortem_ignored": false, "postmortem_published_at": null, "postmortem_notified_subscribers": false, "postmortem_notified_twitter": false, "components": [ { "status": "operational", "name": "Visma.net ERP", "created_at": "2017-01-23T12:03:34.891+01:00", "updated_at": "2020-11-06T15:54:27.262+01:00", "position": 1, "description": null, "showcase": false, "start_date": null, "id": "3hbtn55fszt8", "page_id": "zvpknzcr6znl", "group_id": "m8vwr4m9rzx6" }, { "status": "operational", "name": "Visma.net ERP API", "created_at": "2017-01-31T10:23:50.403+01:00", "updated_at": "2020-11-02T12:53:13.580+01:00", "position": 4, "description": null, "showcase": false, "start_date": null, "id": "k6jrxjnvv3zt", "page_id": "zvpknzcr6znl", "group_id": "m8vwr4m9rzx6" } ] } } An example of a Component Update: { "meta": { "unsubscribe": "http://status.visma.com/?unsubscribe=9j1hhlv61p90", "documentation": "https://help.statuspage.io/knowledge_base/topics/webhook-notifications", "generated_at": "2020-11-09T21:30:34.358Z" }, "page": { "id": "zvpknzcr6znl", "status_indicator": "maintenance", "status_description": "Service Under Maintenance" }, "component": { "status": "under_maintenance", "name": "Visma.net ERP API", "created_at": "2017-01-31T09:23:50.403Z", "updated_at": "2020-11-09T21:30:33.575Z", "position": 4, "description": null, "showcase": false, "start_date": null, "id": "k6jrxjnvv3zt", "page_id": "zvpknzcr6znl", "group_id": "m8vwr4m9rzx6" }, "component_update": { "old_status": "operational", "new_status": "under_maintenance", "created_at": "2020-11-09T21:30:33.583Z", "component_type": "Component", "state": "sn_created", "id": "ndtfcmbh649y", "component_id": "k6jrxjnvv3zt" } }

Florian Haase · ‎22-09-2020

Hi, yes thank you. But I hope you understood why we are to doing so even if you not recommend it. Otherwise we have to introduce a new parameter here in the portal which has to be setup correct dependend on the setup of the number series in Visma.Net. It would be nice and easier if this always would work like expected. Florian

AliMKhan · ‎11-09-2020

Our system is using datetime datatype from sql to store date and time information. This type has a precision of 3.33 milliseconds(see Microsoft documentation: https://docs.microsoft.com/en-us/dotnet/api/system.data.sqldbtype?redirectedfrom=MSDN&view=dotnet-plat-ext-3.1). It doesn't offer a 3 digits milliseconds precision. In practice it will accept only the values having the following pattern: ‘yyyy-MM-dd HH:mm:ss.ff0’, ‘yyyy-MM-dd HH:mm:ss.ff3’, ‘yyyy-MM-dd HH:mm:ss.ff7’. Any value not following this pattern will be rounded to the nearest value that can be represented by datetime. Please be aware of this restriction when sending datetime parameters through API. This restriction will not cause any issues regarding data integrity. The millisecond precision is important when using ‘LastModifiedDateTime’ parameter for data synchronization. For example if you request for data changed since ‘2020-07-22T13:47:02.531’ there will be retrieved data changed since ‘2020-07-22T13:47:02.530’. Then you might end up in a situation of getting some data you already have. This data should be treated as changed data by your system which will replace the old one with the new one. If you request for data changed since ‘2020-07-22T13:47:02.532’ there will be retrieved data changed since ‘2020-07-22T13:47:02.533’. Even though you think you might lose data it will not happen because there is no entry in the database having ‘2020-07-22T13:47:02.532’ as last modified datetime.

AliMKhan · ‎10-09-2020

As communicated before the summer, we will be enforcing throttling to ensure performance and quality for the API. The upper limit for the number of calls will be 15000 calls per hour per integration per company for Production(live) type of API clients. This will be done on 14th of September 2020.

AliMKhan · ‎28-07-2020

Couple of things: maxPagesize has been increased from 100 to 500 on all endpoints. Swagger documentation will be updated in the next release to reflect this. We will introduce pagination on purchaseReceipt and purchaseReceiptBasic endpoint for 8.25. Enforcement of pagination will be in future versions. Following endpoints will have enforced paging for 8.25: /api/v1/cashsale /api/v1/country /api/v1/customerCreditNote /api/v1/customerCreditWriteOff /api/v1/customerDebitNote /api/v1/customerOverdueCharge /api/v1/customerSalesPrice /api/v1/deferralCode /api/v1/employee /api/v1/GeneralLedgerTransactions /api/v1/inventoryadjustment /api/v1/inventoryissue /api/v1/inventoryReceipt /api/v1/inventoryTransfer /api/v1/location /api/v1/payment /api/v1/projectbasic /api/v1/purchaseorderbasic /api/v1/salesordertype /api/v1/supplierPayment /api/v1/vatZone To align maxPagesize for all endpoints, the payment endpoints (customerPayment, supplierPayment and Payment) will have their maxPagesize decreased from 5000 to 500 for 8.25 We would also like to stress that the maxPagesize variable must not be hard coded as it can be changed without notification, based on our monitoring.

AliMKhan · ‎26-07-2020

This is an update on Announcement - Data center migration for Visma.net ERP As you can see at the status page, we have now established a production environment in AWS and have moved all customers, demo and presentation data to AWS. At 12.00 CEST today(26/07/2020), we will open up Visma.net ERP to all customers and partners. This is before the maintenance window is completed. If you have the possibility to test your solutions / integrations today, we would be grateful. We will monitor and follow up during the day, and we expect a peak in activity when we switch the environment live to all customers and partners. This is according to plan. We will monitor this thread during the day, so if you have any feedback, please let us know. Thank you for your help and understanding.

Urgent: Visma.net update regarding Connect Authent...

Re: 5520

Re: Visma.Net Azure Migration Date (Oct 21, 2023 0...

Sv: Timeouts from the InventoryTransfer endpoint

Re: Urgent - Connection to cache service failed

Re: urgent, all API calls returns 500 - internal s...

Inventory endpoint improvement for 8.91 has been d...

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

Sv: Visma.net Financials API updates for version 8...

Re: Throttling policy for "TEST" type "API Client"...

Sv: Lots of 502 and connection errors yesterday an...

Sv: Feedback on webhook notification for maintenan...

Sv: Webhook notifications for Visma Cloud Services...

Re: Override numberseries

MS SQL datetime limitation

Enforcement of throttling policy on 14th of Septem...

Enforcement of pagination on API endpoints and cha...

We are on AWS (All systems are up and running as f...

Visma Community

Over Visma

Volg Visma