About Yıldırım

Yıldırım · ‎23-08-2023

Fixed GET Customer endpoint when filtering on attributes After the 9.57 release, the GET Customer endpoint was not working properly when filtering on attributes. This has now been fixed. API - Due dates for breaking changes Release Notes. Documentation Due Planned removal of VNI authentication method We are planning to phase out VNI authentication method by the end of 2023. ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date. Benefits of this change: - One preferred method of authentication across Visma.net ERP portfolio - Better security using scopes - Let customer be more in control (customer grants access explicitly) More information for ISVs on how to migrate existing integrations and\or setup new integrations can be found in the international developer community: https://community.visma.com/t5/News-in-Developers-Visma-net/Visma-net-ERP-APIs-are-now-available-for-Visma-Connect/ba-p/542148 Dec 31, 2023 Planned removal of Sales Order API endpoints 05.05.2023 - Due date is now changed. We plan to be functional complete by Q2-2024(30th of June 2024), thus new Due date being end of Q4-2024(31st of December 2024). If any change occurred for this, we will announce that as soon as possible, 22.03.2023 - This is now in consideration. New dates for the deadline will come. 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 Dec,31 2024

Yıldırım · ‎23-08-2023

You should exclude the fields, those unintended to be used & with Null values from your payload. Also, please correct your operation field as below. "operation": "Insert",

Yıldırım · ‎22-08-2023

Hi, after consulting with the team, we've checked the company settings, and we're able to POST > Customer Invoice with the service_type token. Following branches are available in the company and can be manually selected in the UI as well. Please control this in your company. Then all the combinations have been POSTED via the API. POST: https://integration.visma.net/API/controller/api/v2/customerinvoice e.g (you can change the values based on your data including "BranchNumber" fields for DocumentHeader & Line level.) { "customerRefNumber": { "value": "777" }, "externalReference": { "value": "46" }, "invoiceLines": [ { "operation": "Insert", "lineNumber": { "value": 1 }, "description": { "value": "Test" }, "quantity": { "value": 1 }, "unitPriceInCurrency": { "value": 500 }, "vatCodeId": { "value": "04" }, "branchNumber": { "value": "031" } } ], "branchNumber": { "value": "031" }, "customerNumber": { "value": "10022" }, "documentDate": { "value": "2023-08-22" }, "hold": { "value": false }, "invoiceText": { "value": "testBranch" } }

Yıldırım · ‎22-08-2023

Based on operation context, timeout can happen, therefore we'd recommend implementing a retry mechanism. If timeouts frequency is increased for the same operation type and data size, please send us the transaction details. (URL - DateTime & ClientID & IppCompanyID) Thanks.

Yıldırım · ‎22-08-2023

You can check available branches for the company by checking it via the Supplier Invoice > Document Line or Financials Details branches. - In our test, we're able to POST Supplier invoice with available branches with Service_Type token. 1) Organization Settings (ScreenId=CS101500) 1.1) Main Org. with 2 Branches 1.2) Secondary org. with 2 branches 2) POST Supplier Invoice (Generated token with Service_API) e.g. to - Main Organization > "02" Branch ✔️ - Main Organization > "021" Branch ✔️ - Secondary Organization > "03" Branch ✔️ - Secondary Organization > "031" Branch ✔️ { "documentType": { "value": "Invoice" }, "date": { "value": "2021-09-16" }, "postPeriod": { "value": "072019" }, "financialPeriod": { "value": "201909" }, "supplierReference": { "value": " VAT UI TEST API1234" }, "description": { "value": "TEST" }, "supplierNumber": { "value": "50000" }, "supplierTaxZone": { "value": "02" }, "creditTermsId": { "value": "14" }, "paymentMethod": { "value": "1" }, "cashAccount": { "value": "1910" }, "branchNumber": { "value": "031" }, "invoiceLines": [ { "operation": "Insert", "transactionDescription": { "value": "Test" }, "inventoryNumber": { "value": "122" }, "quantity": { "value": 1 }, "costInCurrency": { "value": 50 }, "accountNumber": { "value": "3260" }, "vatCodeId": { "value": "01" }, "branchNumber": { "value": "031" } } ] } Financials Output:

Yıldırım · ‎18-08-2023

Hello, please review the document > Getting started with Visma Developer Portal You should be able to integrate with the Sales Order Service API by following each step described in the documentation. If you still need any information, let us know. Thanks.

Yıldırım · ‎18-08-2023

Hi Kristofer, POST/controller/api/v2/customerinvoice If you've checked the company and its branch settings & IDs, and made sure that the specified ID in the payload exists in the company so that it can be selected via Financials ERP UI > Manual Creation of the Customer Invoice, then please review the following information. One can choose a role that a user must have in order to access a branch. This can be configured in the Financials ERP UI <screenID=CS101500" If a role is assigned here, the user associated with the API request must have this role in order for the logic behind to successfully access the branch The issue is, when using the service-API, there is no ordinary user associated with the API request, but rather a system user associated with the integration client. These "users" will not have regular roles. A workaround is to let this field be empty, or set it to "Administrator". This has recently been fixed for the Supplier Invoice, and has also been reported for the Customer Invoice. [Release Notes] - Visma.Net API 9.59.0 - 16.08.2023

Yıldırım · ‎18-08-2023

ℹ️ This has been fixed in [Release Notes] - Visma.Net API 9.59.0 - 16.08.2023

Yıldırım · ‎18-08-2023

Hello, just an update, following is the status of the V3 Sales Order Endpoint on Inventory (Supplier Details). It is set up right now that the supplier data is set to the line if/when the "purchase order source" is specified in the payload, as the supplier is used when creating PO for the order line. So, In order POST SalesOrder V3 to be able to fetch the Supplier data of the selected item, "purchaseOrderSource": "string" should be specified in the payload. https://salesorder.visma.net/swagger/index.html Example: { "type": "SO", "date": "2023-08-18", "description": "Test Sales Order", "customer": { "id": "10022" }, "orderLines": [ { "inventoryId": "1", "description": "Test Sales OrderLine 1", "quantity": 5, "unitPrice": 10, "taxCategoryId": "3", "unitOfMeasure": "STK", "purchaseOrderSource": "purchaseToOrder", "subaccount": { "1": "00", "2": "01", "3": "03", "4": "04" } } ] }

Yıldırım · ‎18-08-2023

1) Please check Item Type and make sure it set in the "General Settings" tab of the item. 2) Have you tried with a different inventory in the payload ? 3) Send your json to us. Thanks.

Yıldırım · ‎17-08-2023

Hello, sorry for the late reply, could you please send your request details to developer@visma.com ? -Request Flow with Operation URLs & Payloads -Ipp-company-id -API ClientID Thanks.

Yıldırım · ‎17-08-2023

Hello, sorry for the late reply, you can try the configuration explained in https://community.visma.com/t5/Forum-in-Developers-Visma-net/API-returns-400-Postcode-is-invalid/m-p/331215/highlight/true#M632

Yıldırım · ‎17-08-2023

Please also check and let us know if the user has multiple active sessions. Thanks.

Yıldırım · ‎17-08-2023

Hei Gert, have you tried to copy-paste the auth URL to incognito ? Also, could you send us that URL via developersupport@visma.com ? "If he's logged out, he does get the login prompt, but after that it again stops at the same point." This sounds like a session issue, do they have another active visma session in the browser during the auth call ?

Yıldırım · ‎17-08-2023

Have you checked Inventory card and its details such as Type, ROTRUT etc. ?

Yıldırım · ‎17-08-2023

Hi, unfortunately we don't have information on how fast this can be resolved, therefore if it's urgent, we recommend using v2 until the fix.

Yıldırım · ‎16-08-2023

Hello, we confirm the issue. This has been registered as a bug, and we'll keep you informed on any progress.

Yıldırım · ‎16-08-2023

Hi, "typeOfWork" is marked as obsolete, therefore it doesn't have any impact in the payload. In the first place, you should be able to create an Invoice with the same values in the Financials ERP UI, otherwise you can not create it via the API. So the error you receive in the UI should be resolved first. When do you receive that error exactly ? Please send the steps & printscreen of the Invoice. Thanks.

Yıldırım · ‎16-08-2023

Release Notes Documentation New endpoint GET api/v2/PurchaseReceipt introduced New endpoint GET api/v2/PurchaseReceipt with higher performance than v1-endpoint is introduced New endpoint GET api/v2/salesorder introduced New endpoint GET api/v2/salesorder has been introduced. This endpoint has a higher performance than the v1 endpoint. New endpoint for adding lines to an open shipment: /api/v1/ shipment/{shipmentNumber}/action/addLine New endpoint for adding lines to an existing shipment: .../api/v1/shipment/{shipmentNumber}/action/addLine. With this, it is now possible to add new lines to open shipments. These lines are automatically added to the original sales order as well. New endpoint /api/v1/ shipment/[shipmentNbr]/action/deleteLine/ [shipmentLineNbr] introduced You can delete a line that was added to a shipment by mistake, by using the new endpoint api/v1/shipment/[shipmentNbr]/action/ deleteLine/[shipmentLineNbr] POST SupplierInvoice “No access to branch” error when service API was used Earlier, when using Visma Service API token with POST SupplierInvoice, the error “No access to branch” was returned. This has now been fixed. API - Due dates for breaking changes Release Notes Documentation Due Planned removal of VNI authentication method We are planning to phase out VNI authentication method by the end of 2023. ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date. Benefits of this change: - One preferred method of authentication across Visma.net ERP portfolio - Better security using scopes - Let customer be more in control (customer grants access explicitly) More information for ISVs on how to migrate existing integrations and\or setup new integrations can be found in the international developer community: https://community.visma.com/t5/News-in-Developers-Visma-net/Visma-net-ERP-APIs-are-now-available-for-Visma-Connect/ba-p/542148 Dec 31, 2023 Planned removal of Sales Order API endpoints 05.05.2023 - Due date is now changed. We plan to be functional complete by Q2-2024(30th of June 2024), thus new Due date being end of Q4-2024(31st of December 2024). If any change would occur for this, we will announce that as soon as possible, 22.03.2023 - This is now in consideration. New dates for the deadline will come. 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 Dec 31, 2024

Yıldırım · ‎15-08-2023

Hi, please try creating the same invoice in the Financials UI so that the system will highlight you the error for the specific area. Also make sure the Inventory used in the customerInvoiceLine has its Type defined in the Inventory card.

Yıldırım · ‎15-08-2023

Hi, if a project has been set in your company and that customer / invoice included in the configuration, then Project-Task field needs to be provided. If not, then you can check "Project accounting preferences" <ScreenId=PM101000> in the UI to see what's the non-project code. When you create a project-related document, you must specify a project task for each document line. If you have specified one of the project’s tasks as the default one for the project, the system will automatically insert this project task in the lines of documents when you select the project.

Yıldırım · ‎15-08-2023

Hello, thanks for reporting, we'll look into this.

Yıldırım · ‎14-08-2023

Summary: 1) Created a New Attribute > Customer Class > Assigned the attribute to that customer class 2) POST New Customer > Assign Attribute Value { "name": { "value": "API - Attribute 05" }, "overrideWithClassValues": true, "customerClassId": { "value": "5" }, "attributeLines": [ { "attributeId": { "value": "NEWCUSTNO" }, "attributeValue": { "value": "txt1" } } ] } 3) Make a GET Request > Filtering Parameter is only "Attribute" {"NEWCUSTNO":"txt1"} https://integration.visma.net/API/controller/api/v1/customer?attributes=%7B%22NEWCUSTNO%22%3A%22txt1%22%7D 3.1) Empty Array Response [] 4) Adding "PageNumber" to the request filtering parameter 4.1) Customer with the attribute matching is retrieved. ---------------------------------------------------------------------------------------------------------- Workaround: Adding PageNumber & PageSize to the GET - Parameters Status: This has been registered as a bug and conveyed to the development team. We will provide further updates as more information is available.

Yıldırım · ‎14-08-2023

Hi Stefan, could you please share your company name & ID ? <developersupport@visma.com>

Yıldırım · ‎10-08-2023

Hello, we're currently investigating this. - How attribute values have been assigned ? Are those new Attributes & values ?

Yıldırım · ‎10-08-2023

Hello, the case has been conveyed to the team, and we're waiting for the investigation. We'll keep you informed.

Yıldırım · ‎03-08-2023

Hi, could you please send your payload and specify request URL / Method ? Thanks.

Yıldırım · ‎02-08-2023

Release Notes Documentation When using no filter for some endpoints, the response includes the entire collection of data instead of the first page with page size=max page size Errors have been found at some endpoints. When no filter is used, the entire collection of data is in the response instead of returning first page with page size=max page size. This has caused performance issues and the problem has been fixed.

Yıldırım · ‎25-07-2023

Release Notes Documentation Performance improvement on API for Purchase order endpoint. The performance of the PurchaseOrder endpoint has been improved up to 17%. Performance improvement on API for Purchase receipt endpoint. The performance of the PurchaseReceipt endpoint has been improved up to 15%. API - Due dates for breaking changes Release Notes Documentation Due Planned removal of VNI authentication method We are planning to phase out VNI authentication method by the end of 2023. ISVs should register their (existing) integrations in the Developer Portal and use Connect authentication instead before the stated end date. Benefits of this change: - One preferred method of authentication across Visma.net ERP portfolio - Better security using scopes - Let customer be more in control (customer grants access explicitly) More information for ISVs on how to migratie existing integrations and\or setup new integrations can be found in the international developer community: https://community.visma.com/t5/News-in-Developers-Visma-net/Visma-net-ERP-APIs-are-now-available-for-Visma-Connect/ba-p/542148 Dec 31, 2023 Planned removal of Sales Order API endpoints 05.05.2023 - Due date is now changed. We plan to be functional complete by Q2-2024(30th of June 2024), thus new Due date being end of Q4-2024(31st of December 2024). If any change would occur for this, we will announce that as soon as possible, 22.03.2023 - This is now in consideration. New dates for the deadline will come. 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 Dec 31, 2024

Yıldırım · ‎24-07-2023

Hi, you can hover your cursor to the cross error mark to see details.

[Release Notes] - Visma.Net API 9.60.0 - 23.08.202...

Re: Create customer invoice faild that the type of...

Re: Branch '1 ' cannot be found in the system

Re: Timeout error - System.Net.Sockets.SocketExcep...

Re: No access to branch when trying to create Supp...

Re: Hämta access code misslyckas

Re: Branch '1 ' cannot be found in the system

Re: No access to branch when trying to create Supp...

Re: Supplier data is not applied to sales order ro...

Re: Create customer invoice faild that the type of...

Re: Stock take issue

Re: Override flags not working for location endpoi...

Re: User login stalls at 'blurry background'

Re: User login stalls at 'blurry background'

Re: Create customer invoice faild that the type of...

Re: Supplier data is not applied to sales order ro...

Re: Supplier data is not applied to sales order ro...

Re: Create customer invoice faild that the type of...

[Release Notes] - Visma.Net API 9.59.0 - 16.08.202...

Re: Create customer invoice faild that the type of...

Re: About task for create customer invoice questio...

Re: Supplier data is not applied to sales order ro...

Re: Attribute in customers

Re: Attribute in customers

Re: Attribute in customers

Svar: Error when creating customer invoices with r...

Re: Salesorder v3 - Freight not included in Order ...

[Release Notes] - Visma.Net API 9.57.0 - 01.08.202...

[Release Notes] - Visma.Net API 9.56.0 - 25.07.202...

Re: How can I See the Error info

Useful pages

About Visma

Contact us

Follow us