About Yıldırım

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

Status: reported (Please subscribe to the News section for release/version information)

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

Hello, Implementation date/plan has not been emerged yet, we'll keep the idea updated of any progress.

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

Hello, POST Sales Order V1 & V2 endpoints return a vague error message when trying to create a Sales Order with an already existing Sales Order: Document Number via the API. HTTP Status Code: 500 "Error creating salesOrder. Object reference not set to an instance of an object." This has been reported to the development team to improve the error message as per the following exception. The Sales Order with Order Number "XXX" already exists. Please use another Sales Order number or update the existing document. Updates will be provided as they become available.(Please subscribe to the News section for release/version information) Thanks.

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

Thanks for the confirmation 🙂

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

Hello, there isn't any endpoint communicates with Workbooks - GL307000 module at the moment. In order to escalate for the implementation, this can be registered in the Ideas part, so that, this will be evaluated by the development team for the future version planning based on the votes. Thank you.

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

Hello Eirik, we've emailed you about the further instructions for diagnosing the issue. Edit: uncheck "Validation" in the segment and try the operation again.

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

Could you make sure that subaccount:segment/value combination has been registered and available at the lookup table in Financials UI ? 1) Check Subaccounts - ScreenID=GL203000 2)Check Subaccount Segment/Value via lookUp table in the Supplier Invoice -Select Subaccount Segment by clicking > Press F3 to check available values for this segment. Thanks.

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

[Release Notes] - Visma.Net API 8.49.0 - 18.05.2021

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

Release Notes Documentation New POST operations on Expense Claim endpoint: put On hold, Submit, Send to approval There is a new improvement on the Expense Claim endpoint. Third party integrators are now able to submit, send to approval and put On hold expense claim using the following new POST operations on the Expense Claim endpoint: - POST /api/v1/expenseClaim/{expenseClaim}/action/hold; - POST /api/v1/expenseClaim/{expenseClaim}/action/submit; - POST /api/v1/expenseClaim/{expenseClaim}/action/approval

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

Hello, In Visma.net ERP Financials, the system automatically performs VAT calculation based on what has been configured in the ERP. Those details should be covered in the company that your integration working with. following process documentation can be helpful. How to set up Vat calculation -About VAT calculation -Set up VAT calculation -About prerequisites and preparation

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

Hello Rene. Currently, there is no endpoint corresponding with Journal reconciliation and relevant module hasn't also been merged with the existing General Ledger Transactions Endpoint, therefore, we recommend you posting this as a new idea by describing the business scenario including the ERP flow. Thanks.

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

@Steinar Møller wrote: The error can be "Error: County '1201' cannot be found in the system". I have tried to post without county and with "county":null, both gives the error. Posting the same in UI also gives error, but in UI you may manually remove or change the value in the county field. Endpoint returns "County '1201' cannot be found in the system" when county field used like "county":null If you'd like to skip assigning a value, you should remove the field from your payload. (Another null values as well) Otherwise, please make sure the used CountyId exists in the Financials ERP. Example: > Click to County selector to change the value , save and then select the requested county again save, to validate. PUT : Customer { "mainAddress": { "value": { "addressLine1": { "value": "Fanahammeren 3" }, "countryId": { "value": "NO" }, "postalCode": { "value": "5244" }, "city": { "value": "Fana" }, "county": { "value": "1221" } } } }

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

Hello, this idea has been planned to be implemented in 8.49 release. Visma.net Financials API updates for version 8.49.0 (May 2021)

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

Release date for 8.49.0 version has been planned as 18/05/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 New POST operations on Expense Claim endpoint: Put On hold, Submit, Send to approval There is a new improvement on the Expense Claim endpoint. Third party integrators are now able to submit, send to approval and put On hold expense claim using the following new POST operations on the Expense Claim endpoint: - POST /api/v1/expenseClaim/{expenseClaim}/action/hold; - POST /api/v1/expenseClaim/{expenseClaim}/action/submit; - POST /api/v1/expenseClaim/{expenseClaim}/action/approval

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

Release Notes Documentation Split location with PUT purchase receipt endpoint Earlier, it was not possible to split location when you run the PUT purchase receipt endpoint. This has now been fixed. The POST SalesOrder V1/V2 endpoint returns an error when 'Free item' is selected on the order line Earlier, when using the POST SalesOrder endpoint, it returned this error message when you had the checkbox 'Free item' selected on the order line: "An item with the same key has already been added". This has now been fixed.

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

Hello Gabriella, currently, this function is not exposed via the API. You can add this as an improvement request to the Ideas section. Thanks.

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

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

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

This issue has been planned to be fixed in 8.48 version. Visma.net Financials API updates for version 8.48.0 (May 2021)

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

Release date for 8.48.0 version has been planned as 11/05/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 Split location with PUT purchase receipt endpoint Earlier, it was not possible to split location when you run the PUT purchase receipt endpoint. This has now been fixed. The POST SalesOrder V1-V2 endpoints returns an error when 'Free item' is selected on the order line Earlier, when using the POST SalesOrder endpoint, it returned this error message when you had the checkbox 'Free item' selected on the order line: "An item with the same key has already been added". This has now been fixed.

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

Hello Steinar, -which Sales Order Endpoint are you using, V1 or V2 ? -Is the performance issue related to a specific company or are you experiencing with other companies as well ? please send us the transaction details including, (developersupport@visma.com) Request Body (JSON) API Client ID ERP Company ID/s Thanks.

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

Hello Steinar, have you tried the solution that is mentioned here, could you please check this out and inform us ? Thanks.

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

Hello, currently, there is no Webhook event defined for the "Inventory Receipts" module that could be "Triggered on status change or custom action" therefore this is not available in the event list. We recommend that you describe the process in detail and post this improvement request in the "Ideas" section. This allows other community members to vote on the idea, which consequently influences the implementation priority / sprint planning process of the development team. Thanks.

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

Hello Patrik, Unfortunately, there isn't any document related to the roadmap that can be shared at this moment. Availability can be checked by comparing the Financials ERP Module : Fields with the API Endpoints : DTOs. (ScreenIDs are labelled in Swagger, might be helpful to find out the correlation between UI & API ) Additionally, we're publishing articles in the News section those are tagged as Upcoming Version News before the final Release Notes. This might also be helpful to see planned fixes / implementations a little in advance.

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

Hello, As of today, Inventory > Stock Items > Replenishment Info Tab. isn't exposed via Inventory Endpoint. This improvement idea can be registered in the Ideas Section. Additionally, there is a tab "Warehouse Details" that has been implemented and available via Inventory Endpoint. We'd recommend checking the fields over to see whether this helps or not. GET: https://integration.visma.net/API/controller/api/v1/inventory?expandWarehouseDetail=true "warehouseDetails": [ { "isDefault": true, "warehouse": "string", "quantityOnHand": 0, "available": 0, "availableForShipment": 0, "lastModifiedDateTime": "2021-05-03T12:36:25.400Z" } ], Visma.net ERP API Documentation: https://integration.visma.net/API-index/

Yıldırım · ‎30-04-2021

Hello Patrik, currently, we get an immediate response as "InProgress / InProcess" with all "release" operation exposed endpoints, due to release action is asynchronous. The process is started in the back end and response is sent back before the process is finished therefore we don't receive the status on whether the document is released/completed. Since this is one of the most frequently requested improvements by the community, we have an improvement case in our backlog for "Creating a mechanism to execute API workloads as a long-running operation". Based on such logic e.g. Long Running Operation with Polling

Yıldırım · ‎30-04-2021

This issue has been planned to be fixed in 8.48 version. Visma.net Financials API updates for version 8.48.0 (May 2021)

Yıldırım · ‎30-04-2021

Release date for 8.47.0 version has been planned as 04/05/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. ------------------------------------------------------------ Update (30/04/2021): Due to an issue found in the release testing we need to postpone the fix below (API:SalesOrder) for the sake of robustness therefore the deployment has been planned for 8.48 version. Will keep you informed about the progress. ------------------------------------------------------------ Release Notes Documentation The POST SalesOrder endpoint returns an error when 'Free item' is selected on the order line Earlier, when using the POST SalesOrder endpoint, it returned this error message when you had the checkbox 'Free item' selected on the order line: "An item with the same key has already been added". This has now been fixed.

Yıldırım · ‎27-04-2021

Release Notes Documentation JournalTransaction endpoint deprecated and replaced with new one The JournalTransaction endpoint is deprecated, and it has now been removed. A new endpoint was created to replace it. See the Swagger documentation for more information under the 'JournalTransactionV2' endpoint. API POST calls returned incorrect location for credit note, credit adjustment or prepayment When sending POST > credit note, credit adjustment, or prepayment via API, the system returned an incorrect location after booking the invoice in the ERP. For example: Instead of returning: controller/api/v1/supplierInvoice/Prepayment/{ref. number} the System returned: controller/api/v1/supplierInvoice/{ref. number} By not adding the document type in the URL, you would not have been able to find your document just created, because your location would have returned a "404 not found" error. This issue has now been fixed and the system returns the correct location.

Yıldırım · ‎27-04-2021

Visma.net Financials API updates for version 8.46.0 (April 2021)

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

Thanks for the confirmation

Re: Known Issue : POST Sales Order V1 & V2 returns...

Re: Make it possible to creake a Kit from Inventor...

Known Issue : POST Sales Order V1 & V2 returns a v...

Sv: Error creating supplierInvoice. Object referen...

Re: endpoint för workbook?

Sv: Error creating supplierInvoice. Object referen...

Sv: Error creating supplierInvoice. Object referen...

Re: Add endpoints to submit and send for approval ...

[Release Notes] - Visma.Net API 8.49.0 - 18.05.202...

Re: Handling of new EU VAT rules

Re: Reconciliation in GET of GeneralLedgerTransact...

Re: County number problem Customer

Re: Add endpoints to submit and send for approval ...

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

[Release Notes] - Visma.Net API 8.48.0 - 11.05.202...

Re: endpoint for "prepare puchase order"?

Re: Problem selecting CashAccount on CustomerInvoi...

Re: API: Problems with updating allocations on pur...

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

Re: Performance issue API

Re: County number problem Customer

Re: Updating inventory balance in third party syst...

Re: Inventory - Replenishment (?)

Re: Inventory - Replenishment (?)

Re: API response - InProcess

Re: Creating SalesOrder - "An item with the same k...

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

[Release Notes] - Visma.Net API 8.46.0 - 27.04.202...

Re: Location response header 404 error for credit ...

Re: Response being cutoff in Shipment endpoint

Useful pages

About Visma

Contact us

Follow us