About Yıldırım

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

Hello, the case has been resolved and the development phase is completed. Unfortunately release date hasn't emerged at this moment. We'll be informing you about the release plan as more information becomes available. Update: This has been fixed in 8.27 Release.

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

A minor update (8.26.01) has been planned to be released for Visma.net ERP / API. Expected downtime for Visma.Net ERP & API (Nov 12, 22:30 CET - Nov 13, 00:30 CET / 2020) Status can be followed at: https://status.visma.com/incidents/mtxg450r71gp The following cases occurred in the 8.26 release are going to be fixed with this update. Visma.net ERP API: Summary Documentation V2/JournalTransactions: MetaData shows incorrect values since 8.26 update In version 8.26.1 an error that returned wrong metadata (totalcount) in the API endpoint JournalTransactionV2 was fixed PurchaseReceipt shows different values for openQty in UI and via API Before when you did a GET request for purchase receipt and you had many receipt to one purchase then API call showed wrong amounts for orderqty, openqty, receiptqty. Now this bug is fixed. Visma.net ERP: Not possible to change the order of the lines on a SO. Earlier, it was not possible to rearrange the sales order lines. This resulted in missing lines on the order confirmation report. This has now been fixed, and historical data affected by this issue have also been resolved. Series id do not fill inn automatically in SO tab Discount details/Feilmelding ved valg av rabatt (mangler sekvens). In version 8.26 of Visma.net ERP, a bug was introduced where the Series ID of the Discount was not updated automatically when the Discount ID was added manually into a Sales order. This is has now been fixed. For further information about ERP Patch details please contact Financials ERP / Community from your market.

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

Hello, Please edit your GET > URL by adding "expandInventoryUnits" parameter and sending "True" as a value. https://integration.visma.net/API/controller/api/v1/inventory?expandInventoryUnits=true Relevant documentation for each module > Endpoint can be found at https://integration.visma.net/API-index

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

Hello Dag, glad to hear the issue has been resolved and it was only connected to missing https.

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

Release Notes Documentation Increased max page size The default /max page size has been temporarily changed from 500 to 1000 for all endpoints where we have pagination and had max page size = 500. New operations for locations on Warehouse endpoint Two new operations have been implemented on the Warehouse endpoint: - POST operation of inventory locations which can be used by integrators for creating inventory locations on warehouses. - PUT operation of inventory locations which can be used by integrators for updating inventory locations on warehouses Change shipping term on purchase orders The field 'Shipping terms' has been added to the Shipping instructions tab of the Purchase orders window. This allows you to change the shipping term for each purchase order, if needed. The shipping term defined on the specific supplier is applied by default. Additionally, the Shipping terms field has been added to the Report designer and to the Purchase order endpoint. See the swagger documentation for additional information related to API. Beta tags removed for v2 endpoints and corresponding v1 endpoints marked as deprecated The following methods are marked as deprecated, and will be removed from May 2021: POST customerCreditNote, customerDebitNote and customerInvoice. The v2 of the same methods, optimized for performance, should now be used instead, and the beta tag for these have now been removed. API calls towards newly provisioned companies not updating user context Earlier, if you provisioned a new company and did API calls towards the newly provisioned company, you could end up on a node where the user context was not updated. This would typically give you a 500 internal server error and if you retried, it worked. The cache handling of user context has been improved so you should not end up in this scenario anymore. Read and create/update descriptions of multi-language supported fields via the API to support webshop and import of items From this version on, there is translation support via API for the Description field in the Stock items and Non-stock items windows with POST, PUT, GET specific translation, GET all translations for a stock item, and DELETE. The system now also supports retrieving a list of all supported languages via API, with information if a language is active and the default. Wrong error message on PurchaseReceipt endpoint when supplier is missing When the supplier was missing from the PurchaseReceipt endpoint, you got an error message saying that a customer number must be specified. Now the error message has been changed to "Error creating purchase receipt. New order must have a supplier number specified." Configuring of manual purchase invoice numbering series with API The configuration of manual numbering for the Purchase invoice numbering series did not sync with API due to a cache issue. In fact, this issue affected all numbering sequences. This has been fixed in the 8.26 release. Purchase Receipt not inheriting currency from the supplier via POST API The Purchase Receipt POST operation did not inherit the currency from the supplier if the currency override setting was disabled. This has now been fixed. The reopenSalesOrder action is not working as expected via API Earlier, the reopenSalesOrder action did not work as expected via API. This has now been corrected, so that it works the same way as in the UI. Posting CustomerInvoice with CashAccount not belonging to the main branch causes issues Posting CustomerInvoice with CashAccount not belonging to the main branch caused issues after the 8.25 release. This has now been fixed. Sales order total gets the wrong total amount when using percentage discount Earlier, the Sales order total got the wrong total amount when using percentage discount via API. This has now been fixed. Invoices from Visma.net Project management get the wrong cash account Earlier, when branch information was used in an invoice, the payment method and the cash account used for the invoice were not set correctly according to how the payment method and the cash account were linked to the branch. This has now been fixed.

Thomas Skjørten · ‎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" } }

Trygve Storrønningen1 · ‎09-11-2020

And that is how it is done 🙂 Setting currency = "NOK" made the difference. Thank you, Visma! 🙂

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

Hello, thank you for the clarification, we confirm that there is an issue with validation on SupplierNumber while sending POST request via API. This is currently allowed and causing erroneous / malformed records in the Financials ERP. We neither have access to your company nor DB. If you could email us informing your Company name and ID (developersupport@visma.com), we can check possibilities with the infrastructure team about how these records can be removed from your company. [Release Notes] - Visma.Net API 8.27 - 17.11.2020

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

@Steinar Møller wrote: Trying 2 GET inventory/{inventoryNumber}, with the specific number RIV2333.5790.1.6. All other inventory numbers are retrieved from the same client. Suppose there are an issue with "." in the end of the number, since we getting same error when testing. InventoryNumber parameter can also be used.

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

Hei, happy to hear that ! 🙂👍

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

Thanks Ivan !

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

Was that financials ERP company or user recently created and roles had been modified ?

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

Hello, the behaviour as Financials ERP follows, once PR Line has been added to a specific supplier invoice and QTY amount modified (e.g. added QTY less than the total QTY of Purchase Receipt) then the same lineNbr no longer selectable in the same invoice > Add Purchase Receipt Line lookup table. Once that invoice is released, user should create a new invoice then the remaining amount of the relevant Purchase Receipt Line (QTY not yet invoiced) will be available in the Add Purchase Receipt Line lookup table and Invoicing Details would have been updated accordingly.

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

Hello, In order to be able to establish document links between Purchase Receipt & Order the following endpoints need to be used. https://integration.visma.net/API-index/ 1) POST an empty Purchase Receipt : POST /controller/api/v1/PurchaseReceipt { "receiptType": { "value": "PoReceipt" }, "supplierId": { "value": "00005" }, "date": { "value": "2020-10-15" } } 2) For Adding Purchase Order to newly created Purchase Receipt POST /controller/api/v1/PurchaseReceipt/{PurchaseReceiptNumber}/action/addpurchaseorder { "purchaseOrders": [ { "orderNbr": "PURCHASE ORDER NUMBER" } ] } 2.1) For Adding Purchase Order Line to newly created Purchase Receipt POST controller/api/v1/PurchaseReceipt/{ PurchaseReceiptNumber} /action/addpurchaseorderlines { "purchaseOrderLines": [ { "orderNbr": "PURCHASE ORDER NUMBER", "lines": [ { "lineNbr": "PURCHASE ORDER LINE NUMBER" } ] } ] } Following aforementioned operations will correctly, transfer Discount Etc fields from the Purchase Order to the Purchase Receipt Lines. establish references between Purchase Order <> Purchase Receipt that can be seen under Purchase Order : Purchase Receipts tab

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

Notifications should be filtered with a valid event_type and date-range or based on NotificationID. For further information, please have a look at Visma.net ERP Webhooks (Event - Subscription - Notification) E.g. Please clean your cookies and re-authenticate at swagger and make sure that you set the correct companyID. If it doesn't help try the same operation with your own API ClientID in any http debugger.

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

Hello, Currently, newly created asset's reference number is returned in the POST > Response Headers "Location". For the lineNumbers, there should be a different logic since there are scenarios of 500+ lines are being POSTED via API so this wouldn't be graceful to include all these line numbers in the response headers. They may even be overridden if user make any changes in the UI. Please register this at the Ideas part then it can be evaluated by the team.

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

Hello, we have the Webhook notifications for Visma Cloud Services Status Page in place, we'd appreciate your feedback about this feature, so please feel free to inform us after trying out 🙂 Webhook feature for Visma Cloud Services Status

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

Hi, Infrastructure team is currently investigating why provisioning of the new user roles were not immediately reflected and started to work again from 2020-10-11 17:39:34.000 and onwards. (https://status.visma.com/incidents/hgk2638tjd8v) Regarding the Visma.Net user is labelled as 'inactive, since this is related to ERP User management we'd recommend contacting your ERP Partner Support to clarify. Thanks.

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 !

Anonymous · ‎06-10-2020

Hi Thomas. You have your developer licence ISV Consili Consulting AB (104682) where you can do your test calls. If you need access, Peter Schalin is your Administrator.

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

As you mentioned, opening a new browser should definitely do the trick since it'll have its own session skipping the CSRF prevention. Anti-Forgery Tokens may not be provided and that's why Dashboard is not allowing those redirections to Start Page where Visma.Net user has already logged in.

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

A minor update has been planned to be released for Visma.net ERP Financials. Expected downtime for Visma.Net API (Oct 6, 22:30 CEST - Oct 7, 00:30 CEST) Status can be followed at: https://status.visma.com/incidents/lpk8p3kh67w8 Postponed to: Thursday, October 8th, 22:30 CEST until Friday, October 9th, 00:30 CEST Visma.net ERP API: When the user invokes POST Supplier Invoice with "unitCostInCurrency" set to "0", Visma.NET ERP has always been taking the default price from the Inventory / Supplier instead of assigning the value "0" sent in the payload. This will be fixed in the patch. ------------------------------------------------------------------------------------------------------------------------------------- Visma.net ERP: Inventory transaction created but not released Missing attachments in Autoinvoice Rutinen skapa inköpsorder / Can not change supplier in PO505000 🇳🇴Kjente feil knyttet til siste release (versjon 8.25, 15. september) For further information about ERP Patch details please contact Financials ERP / Community from your market.

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

Why am I receiving "HTTP 429 - Too many request / throttling" response from API ? After completing the testing phase, you should contact your partner service (How to contact), informing them with your Redirect_URI to obtain Live - Production Client Hello, you can follow up the current status of your Live-Production Type Client request by contacting your partner service kundesenteret@visma.no 🇳🇴

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

You're welcome Andre 👍

Pål Eskerud · ‎30-09-2020

This is important to us as we need to uptate a lot of prices from vendors and would like to do it via the API instead of a rigid importscenario.

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

Patch has been planned to be released for Visma.net ERP Financials. Expected downtime for Visma.Net API (Sep 28, 22:30 CEST - Sep 29, 00:30 CEST) Status can be followed at: https://status.visma.com/incidents/s726231hr7kb For further information about ERP Patch details please contact Financials ERP / Community from your market. ------ Kjente feil knyttet til siste release (versjon 8.25)

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

Hello, Segment Key > Segment Values can be fetched via Dimension Endpoint. https://integration.visma.net/API-index/

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

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

Hello, @Elbert Dannenberg Please refresh the page, it was most likely due to the latest version was not fetched. (8.25.49.1015 ) @adrianm To our knowledge it should still be 6 Months, we'll clarify this with the team and get back to you. Update: Upcoming version news have been updated, and we confirm that endpoint-removal notice period is 6 months.

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

Tonight, Tuesday 21st of September, a minor update has been planned to be released for Visma.net ERP Financials. Expected downtime for Visma.Net API (Sep 21, 22:30 CEST - Sep 22, 02:30 CEST) Details can be found at: https://status.visma.com/incidents/6lcf8clm1qz7 For further information please contact your Financials ERP / Community from your market. Visma.Net ERP Norway Community Mindre oppdatering av Visma.net ERP planlagt natt til tirsdag 22. september.

Re: Problem printing ShipmentConfirmation

Scheduled minor maintenance for Visma.net ERP / AP...

Re: How to determine available units per stock ite...

Sv: Problem med å hente Tolken (obtain Tolken)

[Release Notes] - Visma.Net API 8.26 - 09.11.2020

Sv: Webhook notifications for Visma Cloud Services...

Re: missing vat in orderhead

Re: Post a supplier with a supplier number with le...

Re: Getting error on get inventory based on invent...

Re: API returns 400: Postcode is invalid

Re: Creating invoices programmatically

Re: Creating SupplierInvoice results in empty erro...

Re: Problems uploading receipt payment: supplierIn...

Re: Purchase receipt does not appears in the Purch...

Re: Notification endpoint loading....

Re: Unexpected behaviour in lineNbr for the SalesO...

Re: Webhook message on start/stop maintenance in A...

Re: Error when authenticating against API (for onl...

Re: Customer DELETE endpoint

Svar: Test POST

Re: Integration of portal / User Screens in Dashbo...

Scheduled maintenance for Visma.net ERP (October 8...

Re: Hourly number of requests reached

Re: Total Amount is 0 when adding Purchase Receipt...

Sv: API, Vendor Sales Price endpoint

Scheduled maintenance for Visma.net ERP (Sep 28, 2...

Re: Endpoint for downloading Segment values

Re: reopenSalesOrder: Document not found

Re: What happened to the 6 month notice period

Scheduled maintenance for Visma.net ERP (Sep 21, 2...

Useful pages

About Visma

Contact us

Follow us