About Yıldırım

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

Hello, we've received information from the team. Currently, the Inventory endpoint is only for stock items, as the main idea with it is to get the Availability(On hand, Available for shipping etc) and Availability is only for stock items. It doesn't contain the settings(VAT, item class etc) of inventory. So it is basically for now corresponding to the InventorySummary endpoint in the Financials ERP API (https://integration.visma.net/API-index/) However, we've escalated this as a wish for improvement to extend the endpoint.

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

Release Notes Documentation Project tasks statuses can be updated with the API endpoint PUT/Project/internal When creating project tasks with the API endpoint PUT/Project/internal, the project task status were always set to Active. This has now been fixed and status for the project task can be set to In planning, Active, Completed or Cancelled. Creating a foreign supplier for a Norwegian company working via API Earlier, you were not allowed to create a foreign supplier using POST Supplier endpoint for a Norwegian company. This has now been fixed. Due dates for breaking changes Release Notes Documentation Due Remove deprecated parameters in Financial Period endpoint The numberToRead and skipRecords parameters for the financial period endpoint are deprecated and will be removed. Feb 28, 2023 Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

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

Hello, In the Visma.net.ERP.SalesOrders.Api GET - Inventory endpoint DTO doesn't contain "Type" field, and we also confirm that the endpoint only returns the Stock items. We've informed the SalesOrders.API team regarding this, We're waiting for information on whether this is working as designed or a bug.

Yıldırım · ‎30-11-2022

Hello, we'll check this out and get back to you.

Yıldırım · ‎24-11-2022

Hello Allan, we've completed the investigation and this case has now been conveyed to our infrastructure team to check what can be done to improve the performance in Shipment Endpoint. We'll keep you updated.

Yıldırım · ‎18-11-2022

Release Notes Documentation Changing the address to a foreign one on a domestic supplier not working via API Earlier, when you changed the address of a domestic supplier to a foreign one via API, the change was not working. This has now been fixed. Due dates for breaking changes Release Notes Documentation Due Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎18-11-2022

Thanks, we've received the information. We'll check this out and get back to you as soon as possible.

Yıldırım · ‎18-11-2022

Hi Magnus, it can be related to that hasResponseContent:False depending on the operation. e.g.

Yıldırım · ‎18-11-2022

Hello Alan, is that slowness happening in specific periods, or have you always been experiencing the same performance ? Could you send your API Client ID & ERP Company ID to developersupport@visma.com ? So that we can check our logs to see whether there are any abnormalities. Thanks.

Yıldırım · ‎18-11-2022

Hi, It depends on what UOMs are defined on the selected Inventory and what is used in the payload. Unfortunately, there is no error handling in the current SalesOrder POST endpoint what could show you the number of the line which caused the error. However, in the new Visma.net ERP Sales Order API Endpoint returns the error in detail so that we can see the faulty input based orderLines": [ ] in the response.

Yıldırım · ‎18-11-2022

Hello, the request is still in the backlog, and currently it has not been prioritized. We will provide further updates as more information is available.

Yıldırım · ‎15-11-2022

Hello, the Cash Account ID "6891" shown in the error message is the Account ID of the cash account you've used in the payload "cashAccount": { "Value": "0123" }, This can be found at Chart of accounts(ScreenId=GL202500) When it comes to the error, apparently you don't have access to that account via the "branch": { "Value": "23" }, In order to be able to Create a Customer Payment with specific PaymentMethod and Cash Account, Cash Account/s that you'd like to use with "CustomerPaymentMethod" should be defined under the Payment methods:"Allowed Cash Accounts" in Financials ERP ScreenId=CA204000 regardless of what branch is in use. then this cash account can be selected when creating a customerPaymentMethod. Regarding having multiple branches in your company and if those accounts are defined as branch-specific, Please make sure that "Multi-branch" and "Inter-branch transactions" are active in your licence and enabled in the Financials ERP company. Afterward, go to desired "Cash Account" screenID:CA2020PL and set "restrict visibility with branch : false"

Yıldırım · ‎15-11-2022

Version 9.22.0 has been released. https://status.visma.com/incidents/p83kgwr6gnns Release Notes Documentation Fix on expandSegmentsValues parameter for GET /dimension endpoint The parameter expandSegmentsValues for endpoint /controller/api/v1/dimension/{dimensionId} now returns values correctly when set to True/False. Due dates for breaking changes Release Notes Documentation Due Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎15-11-2022

Hello Magnus, If the endpoint today is asynchronous, meaning that if it is immediately returning a “202-Accepted” HTTP response and starts the actual job in the background, such as “Action” based operations. (Endpoint URL: …/action/…), Currently, the new "Background API" system is also unable to receive the state of the document when the action based request invoked. Therefore, we’re unable to determine whether the “action” based process succeeded or the state of the document changed without making an additional GET request to see the actual status of the document. However, this topic is already in our development plan. (Endpoint logic should be "synchronous" so that, waiting for the actual job to be done, to inform the client accordingly.)

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

That's correct 👍

Yıldırım · ‎09-11-2022

Hello, - What is the request & type registered ? - Are you making the GET State & Content request with the same API client that you've registered the request with ?

Yıldırım · ‎09-11-2022

Hello, ProjectCD and ProjectTaskCD are available in the GET dto and in use by the integrations.

Yıldırım · ‎08-11-2022

This issue has been resolved in [Release Notes] - Visma.Net API 9.21.0 - 08.11.2022

Yıldırım · ‎08-11-2022

Release Notes Documentation Add allocations to kit assemblies to support industries using expiry dates or lot numbers In API, you have the possibility to set the kit allocations for a Kit Assembly (POST / PUT), and you can now use stock items for the assembly to set the allocations for the stock items individually. This is important, for example, for food production where the different ingredients (stock components) used for producing an assembly need to have full control of the allocations, meaning the expiry date. To achieve this, the allocations for each stock component line are now exposed in the API (PUT/POST). Now possible to insert a TransferOrder line in PUT PurchaseReceipt Earlier, it was not possible to insert a TransferOrder line in a PUT PurchaseReceipt endpoint request. This has now been fixed. Due dates for breaking changes Release Notes Documentation Due Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎08-11-2022

Hello Eirik, the field exposed via Sales Order Endpoint (saleOrderUpdateDto) is { "project": { "value": 0 } this field requires the value of the Project's "Internal ID" that can be retrieved from GET Project/{ProjectID} then we should send the following fields in the payload (SalesOrder Header), based on your project defined in the company "project": {"value": 7692} SalesOrderLine "projectTask": {"value": "01"} Example JSON: { "project": { "value": 7692 }, "lines": [ { "operation": "Insert", "lineNbr": { "value": "1" }, "inventoryId": { "value": "122" }, "warehouse": { "value": "1" }, "uom": { "value": "STK" }, "quantity": { "value": 3 }, "note": { "value": "Test Project" }, "projectTask": { "value": "01" } } ], "customerVATZone": { "value": "03" }, "orderType": { "value": "SO" }, "hold": { "value": true }, "date": { "value": "2022-11-08T00:00:00" }, "requestOn": { "value": "2022-11-08T00:00:00" }, "customer": { "value": "10025" }, "location": { "value": "MAIN" } } Financials ERP Output: Project (ScreenId=PM301000) SalesOrder (ScreenId=SO301000) SalesOrderLine We'll inform development team to improve the documentation of the field that to specify it requires the "InternalID" of the project. Regards.

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

Hello jnemo, we've received information from the development team that, write-off documents should be created in the screenID=AR505000 so that API is therefore not capable to handle this operation and returning the same error message. We've registered this case to improve the error message and updating the documentation accordingly.

Yıldırım · ‎02-11-2022

Hello, after consulting this with the team, the recommendation is not using the numberToRead & SkipNumber parameters as it's stated. We're currently working on implementation of Pagination for this endpoint.

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

Release Notes Documentation New GET endpoints in the API for Fixed Asset New GET endpoints in the API for Fixed Asset: fixedAsset fixedAsset/{assetID} fixedAssetTransaction fixedAssetTransaction/{RefNo} fixedAssetClass fixedAssetClass/{classID} fixedAssetPropertyTaxGroup (NL only) fixedAssetPropertyTaxGroup/{propertyTaxID} (NL only) Webhook for salesorder wrongfully triggered for response status 4xx or 5xx when creating shipment via POST endpoint /controller/api/v2/salesorder/{saleOrderNumber}/action/createShipment When you try to create a shipment for a specific sales order with not all lines available in stock, you will no longer get a wrongful webhook notification indicating the sales order status has changed to status 'Shipping'. SalesOrder endpoint returned 500 Internal Server Error instead of 400 Bad Request The POST SalesOrder endpoint now returns the correct 400 Bad Request error instead of the incorrect 500 Internal Server Error when you try to create a sales order with a previously used sales order number. Wrong response status 500 when creating shipment via POST endpoint /controller/api/v2/salesorder/{saleOrderNumber}/action/createShipment When you try to create a shipment for a specific sales order with not all lines available in stock and option "Ship only when complete", you will no longer get the incorrect error response status 500, but a 409 (Conflict) with descriptive message instead. POST PurchaseReceipt and PUT PurchaseReceipt endpoints return error The endpoints POST PurchaseReceipt and PUT PurchaseReceipt no longer incorrectly return an error when the content contains "landedCost". POST PurchaseOrderReceiptBasic endpoint fails in some circumstances Earlier, the POST PurchaseOrderReceiptBasic endpoint was failing in some circumstances. This has now been fixed. Due dates for breaking changes Release Notes Documentation Due Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎26-10-2022

Hello again, we've been informed that by the ERP Team, write-off documents should be created in the screenID=AR505000 and the documents created can be seen under screenID=AR302000 (Bound CustomerPayment Endpoint). However, since that document type exposed via POST Customer Payment Endpoint, that has been escalated to the development team to be reviewed to conclude whether this is a bug. Accordingly, we're expecting to receive information on how that ERP logic should be reflected to the API so that we'll be able to inform you.

Yıldırım · ‎26-10-2022

Hello, unfortunately, we don't have information about the current status of the numberToRead at the moment since it's marked obsolete, we'll check this out and get back to you. Regarding the comment about Accounting module, development is continuing and there is no suspension of any development in that area.

Yıldırım · ‎25-10-2022

Release Notes Documentation Field Bank Detail Type exposed in PaymentMethod endpoint Previously, the Bank Detail Type field was not returned by the PaymentMethod endpoint. This has now been fixed. SupplierPayment endpoint returns wrong data when payments and credit notes have the same reference number Previously, both GET ALL and GET Specific - SupplierPayment endpoints returned the wrong data when payments and credit notes had the same reference number. This has now been fixed, but please note the following: 1.Get ALL SupplierPayment endpoint will return the correct header details and invoice lines applied against each payment document 2. The initial Get SPECIFIC SupplierPayment endpoint (controller/api/v1/SupplierPayment /paymentnumber), in order to be backward compatible, will return only one document, being the payment OR the credit note depending on the used filters. 3. A NEW endpoint Get SPECIFIC SupplierPayment endpoint has been deployed by type and number (controller/api/v1/SupplierPayment /paymenttype/paymentnumber). This one will return the correct information depending on the chosen document. Unable to update a purchase receipt's supplier ID via API Earlier, it was not possible to update "supplierId" in the PUT PurchaseReceipt endpoint. This has now been fixed. SupplierInvoice endpoint not allowing negative retainage Previously, when creating an invoice via API, you were not allowed to enter a negative retainage amount. This has now been fixed. Due dates for breaking change Release Notes Documentation Due Planned removal of Sales Order API endpoints A number of Sales Order API endpoints will be removed as a part of the transition to the next generation ERP. The following API endpoints will be removed: GET /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr} GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/rotrut GET /controller/api/v1/salesorder GET /controller/api/v1/salesorder/{orderType}/{orderNbr}/commissions POST /controller/api/v1/salesorder POST /controller/api/v1/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v1/salesorder/{salesOrderNumber}/action/reopenSalesOrder PUT /controller/api/v1/salesorder/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderNbr} GET /controller/api/v1/salesorderbasic/{orderType}/{orderNbr} GET /controller/api/v1/salesorderbasic POST /controller/api/v1/salesorderbasic PUT /controller/api/v1/salesorderbasic/{orderNbr} POST /controller/api/v2/salesorderbasic POST /controller/api/v2/salesorder POST /controller/api/v2/salesorder/{saleOrderNumber}/action/cancelSalesOrder POST /controller/api/v2/salesorder/{salesOrderNumber}/action/reopenSalesOrder All functionality currently missing in the new Sales Order Service API will be added before these endpoints are removed. The list of affected endpoints will also be extended, so pay attention to future updates. For more information on how to use the Visma.net ERP Sales Order Service, please visit: https://community.visma.com/t5/News-in-Developers-Visma-net/Getting-started-with-the-first-neXtGen-service-Visma-net-ERP/ba-p/401436 Swagger for Visma.net.ERP.SalesOrder.API https://salesorder.visma.net/swagger/index.html Jun 01, 2023

Yıldırım · ‎25-10-2022

Hi Sigbjørn, thank you for letting us know.

Yıldırım · ‎25-10-2022

Hello, we receive the same error message when we try to create a Balance Write-off document in the Financials ERP UI. We've informed the ERP team so that we'll inform you as soon as we receive information.

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

Hello, Currently, Pagination is not available in the Financials Period endpoint and NumberToRead - SkipRecords have been marked as obsolete and will be deprecated, therefore we don't recommend using those filters at the moment. We'll also inform the team to review when Pagination can be implemented to this endpoint.

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

Hello Timo, this post will be moved to the "Ideas" section, and we'll notify the related Partner Service to follow up this improvement request with the team.

Re: Sales Order Api Inventory

[Release Notes] - Visma.Net API 9.25.0 - 06.12.202...

Re: Sales Order Api Inventory

Re: Sales Order Api Inventory

Re: Slow request to confirmShipment

[Release Notes] - Visma.Net API 9.23.0 - 22.11.202...

Re: Slow request to confirmShipment

Sv: How to figure out if a background action faile...

Re: Slow request to confirmShipment

Re: Unit Conversion is missing when creating sales...

Sv: AddressLine3 on Shipment endpoint

Re: Create customerPayment error

[Release Notes] - Visma.Net API 9.22.0 - 15.11.202...

Re: How to figure out if a background action faile...

Sv: ProjectCD and ProjectTaskCD not responding?

Re: Can't access background operation status

Sv: ProjectCD and ProjectTaskCD not responding?

Re: Transfer orders and receipts, part 2

[Release Notes] - Visma.Net API 9.21.0 - 08.11.202...

Re: ProjectCD and ProjectTaskCD not responding?

Re: POST SmallBalanceWo payload

Re: Duplicate and missing rows in financial period...

[Release Notes] - Visma.Net API 9.20.0 - 01.11.202...

Re: POST SmallBalanceWo payload

Re: Duplicate and missing rows in financial period...

[Release Notes] - Visma.Net API 9.19.0 - 25.10.202...

Sv: Problems with access to ReportId when getting ...

Re: POST SmallBalanceWo payload

Re: Duplicate and missing rows in financial period...

Re: nextGen API POST https://salesorder.visma.net/...

Useful pages

About Visma

Contact us

Follow us