About Yıldırım

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

Hello, you have some syntax errors in your payload. We've edited the JSON based on your inputs that you can see below. Additionally, you have to send "WarehouseID" in the request because this is a mandatory field for the Inventory Issue. POST: /controller/api/v1/inventoryissue { "issueLines": [ { "warehouseId": { "value": "1" }, "unitCost": { "value": 666 }, "tranType": { "value": "Issue" }, "operation": "Insert", "inventoryNumber": { "value": "HC1026MS" }, "locationId": { "value": "1" }, "quantity": { "value": 1 }, "description": { "value": "InventoryIssueLine" } } ], "date": { "value": "2023-10-06" }, "description": { "value": "testInventoryIssue" } }

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

Please inform the client to try that operation with the same values in their company so that you can diagnose the case.

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

Hello, Customer > General Information > Country is a mandatory field. That field is automatically populated, even creating a new Customer in the UI, therefore we can not override the value with null. This is valid for all related Country fields, also not possible with on-the-fly entry.

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

Hello, have you tried creating IN type Order with the same values in the Financials Company UI ?

Yıldırım · ‎28-09-2023

Hello, we're unable to reproduce the issue. Regardless of the pageNumber, the whole data should be filtered based on the query param. Could you please send us your company-ID & API Client details with DB restore approval ? <developersupport@visma.com>

Yıldırım · ‎28-09-2023

Hello, this post will be moved to the ideas section to be reviewed by the development team.

Yıldırım · ‎28-09-2023

Hello, "DiscountAmount" is calculated based on "DiscountPercent" of the unitPrice - Manual amount total. E.g: manualAmount = 300 discountPercent = 20 discountAmount = 60 So you should use one of them to adjust your discount if there is no automatic discount has been configured for either item or customer.

Yıldırım · ‎28-09-2023

Hi, that's correct. Currently "Original Document" nr is not available. We'll move this post to the ideas section to be reviewed by the development team.

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

Release Notes Documentation Error on subaccount when creating customer with invoicePOST CustomerInvoice V2 with restriction group setup When having access restriction on accounts and subaccounts, but you didn't use those accounts and subaccounts when sending an API POST operation for CustomerInvoice endpoint, the system showed an error that subaccounts do not exist. This has now been fixed, and the sales invoices sent using API POST operation for CustomerInvoice endpoint are created in the system with the correct accounts and subaccounts. This will be first enabled for PILOT customers. SupplierInvoice Endpoint error - "Do you want the system to recalculate the amount(s) in the cost column" If the Supplier (AP303000), which was targeted, used the Gross or Net tax calculation modes, the call launched an error on recalculation on the line. This was caused by the recent implementation enabling to link purchase receipt lines multiple times into purchase invoice documents, which did not allow the line recalculation to be executed. 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 · ‎06-09-2023

SupplierInvoice endpoint - Purchase receipt line can now be added or linked more than once inside the same purchase invoice document Behaviour implemented in the Purchase invoices (AP301000) window with earlier version 9.60. With version 9.61, the implementation is included into the SupplierInvoice API endpoint. Purchase receipt line can now be added or linked into multiple invoice lines inside the same purchase invoice document with POST and PUT operations. 9.61.0 GET operation for "customerOverdueCharge" endpoint with parameter "expandApplications=true" returns all application details related to customer Overdue Charge When using the GET operation for "customerOverdueCharge" endpoint with parameter "expandApplications=true", the system didn't give any details in the response message. This has now been fixed and third party integrators will get all application records related to the customer overdue charges in the response message under the application section. If the parameter is not set or is set as False, the response message will not contain any application details. 9.61.0 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 · ‎06-09-2023

Since when are you experiencing this ? What token are you using ? Do you make a parallel or consecutive (short interval) calls to the same endpoint ? Please send your application details and companyID to us.

Yıldırım · ‎06-09-2023

Hi, you can read the recently created object's value via Response Headers > Location https://community.visma.com/t5/Knowledge-base-in-Developers/How-to-read-recently-created-object-ID-from-Visma-Net-API/ta-p/273520

Yıldırım · ‎06-09-2023

Hi, most of the endpoints have fields related error handling, for sure in some cases they might be vague. In those cases, by far the best option is trying the same operation with the same values in the UI, so that the system can highlight the error with more information. Yes, we have a plan for moving all the endpoints over time, meantime we're still working to improve existing endpoints.

Yıldırım · ‎05-09-2023

Hi David, in V2, unfortunately we don't have error handling such as Line specification etc. The more detailed error / tracking schema is available with Sales Order Service API <https://salesorder.visma.net/swagger/index.html>

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

Hello, tested the case again today, I'm able to POST Supplier Invoice without receiving Branch not found error. If you're still receiving the error, we might need to specifically check your company & integration setup, so please contact us via developersupport@visma.com and share your companyID & Application details from the developer portal. Thanks.

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

Thanks for the confirmation Ronny.

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

Hi, tested it again after a day of the setup, and it is working, I'll wait a little longer before testing it again. Configuration: 1) Created a custom User Role & Assigned the user/s 2) Restricted the access with the User Role 3) Re-generated a service_type Token 4) POST Supplier Invoice to User Role restricted branchID: "03" { "documentType": { "value": "Invoice" }, "date": { "value": "2023-08-29" }, "postPeriod": { "value": "082023" }, "financialPeriod": { "value": "202308" }, "supplierReference": { "value": " VAT UI TEST API12345" }, "description": { "value": "TEST" }, "supplierNumber": { "value": "50000" }, "supplierTaxZone": { "value": "02" }, "creditTermsId": { "value": "14" }, "paymentMethod": { "value": "1" }, "cashAccount": { "value": "1910" }, "branchNumber": { "value": "03" }, "invoiceLines": [ { "operation": "Insert", "transactionDescription": { "value": "Test" }, "inventoryNumber": { "value": "122" }, "quantity": { "value": 1 }, "costInCurrency": { "value": 50 }, "accountNumber": { "value": "3260" }, "vatCodeId": { "value": "01" }, "branchNumber": { "value": "03" } } ] } 5) Financials output:

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

Thanks Ronny

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

Hi, there is not much we can catch from the API error, therefore the best way to diagnose this issue would be checking this error in the ERP UI.by manually following the process. So that, UI would highlight the error in detail.

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

Hi Sitter, after some testing, I was able to Release it without error: "Scope requirement not met" POST: https://integration.visma.net/API/controller/api/v1/customerPayment/400069/action/release RequestBody: { "type": { "value": "Payment" } } You should grant "vismanet_erp_service_api:update" scope to your application and generate a new token after. (including that scope in the token request together with read - write - delete)

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

Hei Oleg, I see your point, then could you also share your requests with urls and possibly payloads for POSTs, so that maybe we can figure out something else. Thanks ! (It'd be great If you could specify the transaction order & flow )

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

I see, thanks for the information. Perhaps this is also related to user access issue connected with service_type token. We'll investigate this and prepare a fix.

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

1) "Available" or "OnHand" : The quantity of the stock items available at the specific warehouse and location. I think first you can fetch this value from the Inventory Summary to compare WMS <> Visma ERP. 2) Then, based on ERP company flow, (Either Receipt or Issue) you can check, InIssues & InReceipts. Considering,ERP Company released the documents, put some delay such as up to 5 seconds (This may vary depending on the size of the document so that how long the initial document release operation takes in the system) 3) After getting the value, update your WMS accordingly. Note: You can also check new https://salesorder.visma.net/swagger/index.html (Inventory Endpoint) for the same operation to see if that endpoint provides more parameters. Performance wise, the new endpoint should be better than the current endpoint. --------------------------------------------------------------------------------------------------------- onHand: The quantity of the stock item available on hand at the specified warehouse and location. inIssues: The quantity of the stock item included in the inventory issue documents that have not yet been released. This quantity affects the available quantity only if the Deduct qty. on issues option is selected for the item class in the Item classes (IN201000) window. inReceipts: The quantity of the stock item included in the inventory receipt documents that have not yet been released. This quantity affects the available quantity only if the Include qty. on receipts option is selected for the item class in the Item classes (IN201000) window. inTransit: The quantity of the stock item included as in-transit quantities in the inventory transfer documents that have not yet been released. This quantity affects the available quantity only if the Include qty. in transit option is selected for the item class in the Item classes (IN201000) window. ---------------------------------------------------------------------------------------------------------

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

Hi, 1) Please make sure that Tenant(company) has granted the following scopes. (Service_Type Applicaton Example, if your application is web application then follow the same steps for the Interactive_API type.) 2) Generate a token with the granted scopes.

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

Hei, sure, could you please share that custom user setup (Steps you've followed etc.) via developersupport@visma.com ? To make sure that I'll apply the same config.

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

Hi Stefan, FYI, https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Visma-Net-API-9-60-0-23-08-2023/ba-p/599253

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

Update: Development team checked the database of this customer and: Restriction groups are inactive now. Restriction by GLaccount shows that accounts 3911 and 3230 are restricted A inverse in 2 groups ("Kb ej noll invert", "Kst ej noll invert"), Restriction by subaccount show that subaccounts 937-999000-00-0000 and 931-999000-00-0000 do not have restrictions. Restriction by subsegment shows that: segmentID 1 with segment value 000 is restricted to group "Kst ej noll invert" and segment value 937 and 931 are not restricted segmentID 2 with segment value 000000 is restricted to group "Kb ej noll invert"and segment value 999000 is not restricted segmentID 3 with segment value 00 is restricted to group "Bolagskod ej noll invert" segmentID 4 with segment value 0000 is not restricted Because Restriction groups are inactive now, when testing the API json POST customer invoice, it works and the system creates the invoice. When activating the groups "Kb ej noll inverta" and "Kst ej noll invert" the Restriction by GL account for accounts 3911 and 3230 get activated and the Restriction by subsegment segmentID 1 with segment value 000 and segmentID 2 with segment value 000000 get activated. When testing the API json POST customer invoice, we get an error "message": "VismaId: 14a2619c-9e1d-47a0-b8e8-8660659e6e99. Error creating document. Error: Kostnadsställe of SubID do not exist." even if the subaccounts 937-999000-00-0000 and 931-999000-00-0000 are not restricted. This is reproducible on the company database.

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

Hello, you can find additional information about the fix and the background of the case below. 1) https://community.visma.com/t5/Forum-in-Developers-Visma-net/Sales-orders-V3-created-by-id/m-p/584084#M3699 2) POST Sales Order Service API - "createdById" and "lastModifiedById" set with API_Client_ID [Release Notes] - Sales Order Service API 1.0.14.648

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

Hei Oleg, sounds like a plan, but first I'd like to establish a such flow in our test company and have a couple of test runs before confirming that It'd serve the purpose. I'll get back to you soon.

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

Hi, I've added "Administrator" role and did POST, it works, however I'll wait 2–3 days as you mentioned and test this again.

Re: Error creating inventory issue. Error: 'Locati...

Re: Error: Invoice contact Revision ID cannot be e...

Re: Unable to empty an optional address (Billing o...

Re: Error: Invoice contact Revision ID cannot be e...

Re: Setting financialPeriod for CustomerInvoice Ge...

Re: Missing fields in the location enpodpoint

Re: Negative discountPercent when creating credit ...

Re: CustomerCreditNote - Origin ref number

[Release Notes] - Visma.Net API 9.64.0 - 28.09.202...

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

Re: Random SQL-errors from journaltransactions

Re: JournalTransactionV2: get JournalNumber of new...

Re: Better Error messages

Re: Better Error messages

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

Re: ROT/RUT error on confirmShipment

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

Re: ROT/RUT error on confirmShipment

Re: ROT/RUT error on confirmShipment

Re: Cant release customer payment with new token

Re: Stock take issue

Svar: Cant release customer payment with new token

Re: Stock take issue

Re: Cant release customer payment with new token

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

Re: Attribute in customers

Re: Error when creating customer invoices with res...

Re: Strange ID for "last edited by"/"Created by" i...

Re: Stock take issue

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

Useful pages

About Visma

Contact us

Follow us