About Yıldırım

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

Override Visma.net Financials ERP number-series via API function has been implemented in Visma.net Financials ERP API version 8.25 (September 2020) With this function, we can set different asset number / ID via API than the Number-series that have been configured in the Visma.net Financials ERP UI without breaking the auto-numbering sequence. Currently, available in the following endpoints POST Customer POST CustomerDebitNote V2 POST SalesOrder POST Supplier POST Journal Transaction V2 POST PurchaseOrder POST Supplier Invoice POST CustomerCreditNote V2 POST CustomerInvoice V2 How to set it up? 1) Set "Allow manual numbering on imports" true in the Visma.net Financials ERP UI. (Number Series - ScreenId=CS201010) 2) Include the following key-value pairs in the payload based on the aforementioned endpoint DTO syntax. ("ReferenceNumber" field may vary depending on the resource.) Visma.net ERP API - Endpoint Documentation ... "overrideNumberSeries": { "value": true }, "referenceNumber": { "value": "string" } ... After a successful POST request, the value specified in the "ReferenceNumber" field would be assigned to the resource as an identifier. Afterward, the end-user or any integration can continue using Financial Company's automatic numbering setup in the transactions without any number skipped from the defined number series.

RMaarssen · ‎25-03-2021

Thanks, we will always provide "retainagePct": { "value": }, "curyRetainageAmt": { "value": }, 🙂

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

The Idea will be followed on: Extend Sales Order Endpoint PUT operation's SOOrderLine pointer with "External-Link" Field

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

Financials Company ID has no connection with your API Client ID therefore one cannot understand or pick your API Client ID by looking the Company ID that you sent transaction via the API. API Throttling is applied per API Client Type as it's stated in the articles, 1) Visma.Net Integrations - API Client Types & Configuration 2) Why am I receiving "HTTP 429 - Too many request / throttling" response from API ? 3) Background Information on API Client & Token & Visma.net Financials User & Company So, - if you have a Test Type API Client then, a token generated with "X " API Client ID has 1 Hour / 500 requests per company (ipp-company-id) - if you have a "Live" - Production Type API Client then, a token generated with "Y" API Client ID has 1 Hour / 15000 requests per company (ipp-company-id) If you believe you've not reached out to throttling threshold, please contact VNI-Support@visma.com by specifying your API identity. (API CLIENT ID that is used to generate a token. & API requests made with that token to the specific company)

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

Hello Steinar, You should use the parameter showNotes=true for Get a range of SO Orders https://integration.visma.net/API/controller/api/v1/salesorder?showNotes=true

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

Hello, One currency ID can only have one exchange rate with the same Currency / Currency Type / Effective Date / Currency Rate at the same time. In this way, as it mentioned above, this can be fetched via e.g. https://integration.visma.net/API/controller/api/v1/currency/exchangerates/EUR/2021-03-22 Currency exchange rates can be recorded any time for a particular currency. Each record contains the date when the rate becomes effective. When the next record for the same rate type is entered, the rate value becomes a historical rate and can be used as the effective rate for operations that take place between the two dates. Historical rates are stored in the database for all the financial years defined in the system. We do not recommend that you change the value of the exchange rate if any transactions were based on the historical rate. You can use the historical rates for entering back-dated transactions and for calculating realized and unrealized gains and losses.

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

Hello, This feature is currently available on the following endpoints, so please make sure you are using the "overrideNumberseries" on POST CustomerInvoice V2. POST Customer POST CustomerDebitNote V2 POST SalesOrder POST Supplier POST Journal Transaction V2 POST PurchaseOrder POST Supplier Invoice POST CustomerCreditNote V2 POST CustomerInvoice V2 Visma.net Financials API updates for version 8.25 (September 2020) Override number series for POST CustomerInvoice V2 You are now able to override the number series of a customer invoice by specifying the field overrideNumberSeries=true when creating a customer invoice. This functionality has to be enabled in the Number series (CS201010) window by selecting option Allow manual numbering on imports. You also can specify a longer customer invoice number when using overrideNumberSeries than what is specified in number series for customer invoice. 1-Set Allow manual numbering on imports = true on the UI 2-Set "overrideNumberSeries": { "value": true }, 3-Add "referenceNumber": { "value": "string" },

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

Release Notes Documentation Create transfer receipts through POST Purchase receipt endpoint You are now able to create transfer receipts through POST Purchase receipt endpoint. The GET customer endpoint does not return all customers Earlier, in some cases, when using the GET method on the customer endpoint, not all customers were collected. There were some issues in how the data being retrieved. This has now been fixed. Unhandled exception in the CustomerInvoice V2 endpoint Earlier, an unhandled exception was thrown by the CustomerInvoice V2 endpoint, when the fields "startDate" and "endDate" were included in the POST payload. This has now been fixed. The GET warehouse endpoint returns warehouseID with trailing spaces Earlier, the GET warehouse endpoint returned warehouseID with trailing spaces. This has now been fixed, and the warehouseID will not contain any trailing spaces any more in the response.

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

Visma.net Financials API updates for version 8.41.0 (March 2021)

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

Release date for 8.41.0 version has been planned as 16/03/2021 17:00 CET. Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release. Release Notes Documentation Create transfer receipts through POST Purchase receipt endpoint You are now able to create transfer receipts through POST Purchase receipt endpoint. The GET warehouse endpoint returns warehouseID with trailing spaces Earlier, the GET warehouse endpoint returned warehouseID with trailing spaces. This has now been fixed, and the warehouseID will not contain any trailing spaces any more in the response. The GET customer endpoint does not return all customers Earlier, in some cases, when using the GET method on the customer endpoint, not all customers were collected. There were some issues in how the data being retrieved. This has now been fixed. Unhandled exception in the CustomerInvoice V2 endpoint Earlier, an unhandled exception was thrown by the CustomerInvoice V2 endpoint, when the fields "startDate" and "endDate" were included in the POST payload. This has now been fixed.

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

Release Notes Documentation Restructure, introduce pagination and improve the performance for GET stocktake endpoints The response DTO (Data Transfer Object) has been restructured, pagination is introduced, and the performance for GET stocktake endpoints has been improved. To avoid breaking the current integrations, all changes have been put under V2. Also, the PUT stocktake endpoint has been duplicated under V2, and all existing stocktake endpoints have been marked as obsolete. Both V1 and V2 will be supported for the next 6 months. The GET CustomerPayment endpoint returns incorrect document type Earlier, the GET CustomerPayment endpoint returned incorrect document type in some situations. This has now been fixed.

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

This is the information that we received from the infrastructure team about how that specific exception is built. If there are inconsistencies in the scenarios of when the exception thrown, please inform us on the followed steps before you've received the response so that we can check this out in detail.

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

Release date for 8.40.0 version has been planned as 09/03/2021 17:00 CET Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release. Release Notes Documentation The GET CustomerPayment endpoint returns incorrect document type Earlier, the GET CustomerPayment endpoint returned incorrect document type in some situations. This has now been fixed. Restructure, introduce pagination and improve the performance for GET stocktake endpoints The response DTO (Data Transfer Object) has been restructured, pagination is introduced, and the performance for GET stocktake endpoints has been improved. To avoid breaking the current integrations, all changes have been put under V2. Also, the PUT stocktake endpoint has been duplicated under V2, and all existing stocktake endpoints have been marked as obsolete. Both V1 and V2 will be supported for the next 6 months.

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

We would like to be able to set "Same as Main" : InvoiceAddress checkbox in GET-PUT-POST operations via the Customer Endpoint.

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

Release Notes Documentation Wrong response code when confirming shipment Earlier, when you confirmed a shipment from the API, in some scenarios you got the response code "200 OK", even though the confirm shipment operation was not successful. This has now been fixed. Insert and delete lines when using the PUT method on the stocktake endpoint Earlier, it was not possible to insert and delete lines when using the PUT method on the stocktake endpoint. This has now been fixed.

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

Hello Thomas, we also encourage you to use our Ideas Section to raise your improvement requests, thus, the idea would be visible to the development team for the sprint planning and can be prioritized based on demand rate. Thanks.

Anonymous · ‎02-03-2021

Hi Yildirim, Yes, that's the correct one Kind regards Jon-Erik

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

Release date for 8.39.0 version has been planned as 02/03/2021 17:00 CET Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release. Release Notes Documentation Insert and delete lines when using the PUT method on the stocktake endpoint Earlier, it was not possible to insert and delete lines when using the PUT method on the stocktake endpoint. This has now been fixed. Wrong response code when confirming shipment Earlier, when you confirmed a shipment from the API, you got in some scenarios the response code "200 OK", even though the confirm shipment operation was not successful. This has now been fixed.

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

Hello Andre, as Magnus mentioned, recommended way would be dividing your request into chunks, such as 250 - 500 Line per request. [Initial POST then PUT (Insert Invoice Lines) ] Can you also please send your CompanyID & Name and the API Client ID used in your integration ? In this way we can check our logs to see if there is anything related to the servers. Thanks. <developersupport@visma.com>

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

Hello Tomi, This improvement request is in our backlog and the posted "Idea" can be found at Webhook subscription for Purchase receipt Please feel free to add comment and give kudos which will eventually help our development team with prioritization during the sprint planning. Thanks.

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

Hello Mathias, Could you please send us your integration's API Client ID that is used while generating the token ? You can send this to developersupport@visma.com CompanyName seems to be "Skal", could you confirm ? Thanks.

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

Release Notes Documentation Related inventory issues are not automatically released when releasing customer invoices via API Earlier, when calling a release operation for a customer invoice (SO303000) via API, the related inventory issue was not automatically released. This has now been fixed.

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

Please pay extra attention to the above shared information and the format. "location": { "value": "yourLocationID" },

Anonymous · ‎22-02-2021

Hi Florian Thanks for your feedback. Will forward this to my colleagues.

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

Visma.net Financials API updates for version 8.38.0 (February 2021)

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

Release date for 8.38.0 version has been planned as 23/02/2021 - 20:00 CET Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release. Release Notes Documentation Related inventory issues are not automatically released when releasing customer invoices via API Earlier, when calling a release operation for a Customer invoice (SO303000) via API, the related inventory issue was not automatically released. This has now been fixed.

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

Release Notes Documentation GET Customer no longer returns metadata (MaxPageSize,TotalCount) After the 8.36 release, GET Customer did not return the metadata (MaxPageSize, TotalCount) array in the response. This has now been fixed.

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

This improvement request is about Visma.net ERP API endpoints that allows attachments to be uploaded to the ERP. The swagger JSON that is generated from these endpoints do not contain the necessary metadata to generate a correct client code. Currently, Swagger-UI cannot be used to test these Attachment endpoints to upload files, since a file upload control is not generated. This should be implemented.

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

Release date for 8.37.0 version has been planned as 16/02/2021. Release plan & date may vary. We will keep you informed of any changes. This thread will be updated regularly up until the point of version-release. Release Notes Documentation GET Customer no longer returns metadata (MaxPageSize,TotalCount) After the 8.36 release, GET Customer did not return the metadata (MaxPageSize,TotalCount) array in the response. This has now been fixed.

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

Thanks, Florian, and we're sorry for the issues this has caused.

How to override Visma.net Financials ERP number-se...

Re: Retainage not applied when POSTing a SupplierI...

Re: External link for post in screen AR301000 - St...

Re: Error 429 Too Many Calls

Re: SalesOrder note field

Re: Which exchange rate is leading

Re: manual invoice numbering through API and autom...

[Release Notes] - Visma.Net API 8.41.0 - 16.03.202...

Re: Using start / end date in the API when creatin...

Visma.net Financials API updates for version 8.41....

[Release Notes] - Visma.Net API 8.40.0 - 09.03.202...

Re: Deleting purchase receipt lines gives GUI erro...

Visma.net Financials API updates for version 8.40....

Expose "Same As Main" flag in Customer Endpoint : ...

[Release Notes] - Visma.Net API 8.39.0 - 02.03.202...

Re: Combining Payment types into one query possibl...

Re: Add 'Remaining Credit Limit' to the GetCustome...

Visma.net Financials API updates for version 8.39....

Re: Posting Supplier invoices with large number o...

Re: Webhooks: purchace receipt

Re: Periodically Timeouts

[Release Notes] - Visma.Net API 8.38.0 - 23.02.202...

Sv: Trying to change location for a sales order

Re: Customer endpoint: Records missed under certai...

Re: Issues not automatically released through API

Visma.net Financials API updates for version 8.38....

[Release Notes] - Visma.Net API 8.37.0 - 16.02.202...

Swagger json is missing Form-Data information for ...

Visma.net Financials API updates for version 8.37....

Re: metadata totalcount missing in Customer endpoi...

Useful pages

About Visma

Contact us

Follow us