About Yıldırım

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

[Release Notes] - Sales Order Service API 1.0.14.638

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

Release Notes Documentation Fix Version/s POST SupplierInvoice not allowing inserts when restriction groups are set active, if restrictions were limiting the default subaccount for new row entries When the settings from General ledger account access (GL104000) were set to limit the access towards subaccount segments, the insert via POST operation could not process the request, when validation identified the default inputs into the row momentarily placed against user limited combination. This has now been fixed, and the allowed subaccount combinations can be inserted with POST operation without default line entries for the subaccounts affecting the insert coming via API. The fix has been added under a feature toggle and will be initially activated only for specific companies. 9.53.0 API - Due dates for breaking changes 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 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

JacobIpsen · ‎29-06-2023

i Got it working my local cashe where playing a trick on me Ctrl+Shift+R got it working. have u seem my question regarding findings in regards to warehouse and toWarehouse filtes ? it seems like toWarehouse filter only works if used WITH warehouse and not alone is this intended ?

Magnus Johnsen · ‎26-06-2023

Alright, please do. Thank you.

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

Hello, could you please report this to channel: VNI-Support@visma.com including developersupport@visma.com in the cc ? Thanks.

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

Hei Rene, I've received the email so that we'll check and inform you accordingly. Thanks !

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

This can also be related to that, we're unable to edit Purchase Order when it's Hold:False so I'd recommend trying updating the line by sending only the values for the fields you'd like to update, then sending another PUT for Hold:false.

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

Hi Iryna, unfortunately, "PaymentMethod" field is not exposed via POST & PUT api/v2/customerCreditNote atm. You can register this as an improvement Idea so that this could be reviewed by the development team.

Snuffsis · ‎21-06-2023

Yes, it seems like it. But then the question here might be why it seems like the input for financialPeriod seem to get scrambled in the backend for the endpoint? I would understand if it answered with "Post period value 12-2020 General ledger error: ..." But now it scrambles it an ends up being "20-1220"

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

Release Notes Documentation Fix Version/s Branch filtering for JournalTransaction endpoint to be applied on transaction instead of batch At this moment, the Branch filter on the JournalTransaction endpoint is applied on batch level. It will be switched to be applied on transaction level instead of batch. 9.52.0

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

Hello Lema, that's correct. Are you using the Developer Portal & App store ?

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

Hello Iryina, this is "DeferralCode" that can be found in both GET CustomerInvoice and CustomerCreditNote Endpoints

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

Hi,could you please share your payload with us ? (developersupport@visma.com) Thanks.

sallbergerik · ‎14-06-2023

Yes, it worked to create the sales order now when I tried!

thingsio · ‎14-06-2023

Hi, We use https://integration.visma.net/API/controller/api/v1/inventoryissue and the following data according to the documentation: { "issueLines": [{ "operation": "Insert", "tranType": { "value": "Issue" }, "warehouseId": { "value": "gro" }, "lineNumber": { "value": 0 }, "inventoryNumber": { "value": "13003" }, "quantity": { "value": 7 }, "uom": { "value": "STUK" }, "reasonCode": { "value": "2" } }], "date": { "value": "2023-05-03T10:07:16.563" } } For any logistics company it is really important to be able to see a date when an Inventory issue is changed. Can we get back to the original problem? How can we change the inventory by using the API and also show a date when that is done? Cheers and thanks!

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

Here you can see an example payload for the POST Credit Note V2 { "currencyId": { "value": "NOK" }, "customerRefNumber": { "value": "test custRef" }, "externalReference": { "value": "test extRef" }, "project": { "value": "X" }, "lines": [{ "operation": "Insert", "inventoryNumber": { "value": "1" }, "lineNumber": { "value": 1 }, "description": { "value": "line1" }, "quantity": { "value": 10 }, "unitPriceInCurrency": { "value": 50 }, "manualAmountInCurrency": { "value": 50 }, "accountNumber": { "value": "3000" }, "vatCodeId": { "value": "3" }, "uom": { "value": "STK" }, "subaccount": [{ "segmentId": 1, "segmentValue": "0" }], "note": { "value": "lineNote" } }], "applicationLines": [{ "operation": "Insert", "documentType": { "value": "Invoice" }, "refNbr": { "value": "000039" }, "amountPaid": { "value": 50 } }], "customerVatZoneId": { "value": "01" }, "invoiceAddress": { "value": { "overrideAddress": { "value": true }, "addressLine1": { "value": "adr1" }, "addressLine2": { "value": "adr2" }, "addressLine3": { "value": "adr3" }, "postalCode": { "value": "7005" }, "city": { "value": "city" }, "countryId": { "value": "NO" }, "county": { "value": "1601" } } }, "invoiceContact": { "value": { "overrideContact": { "value": true }, "name": { "value": "xxx" }, "email": { "value": "xxx@xxx.com" }, "phone1": { "value": "11111" } } }, "customerNumber": { "value": "10000" }, "documentDate": { "value": "2020-05-06T10:46:10.777Z" }, "hold": { "value": false }, "postPeriod": { "value": "052021" }, "financialPeriod": { "value": "202105" }, "invoiceText": { "value": "invText" }, "locationId": { "value": "MAIN" }, "note": { "value": "Test Note" }, "cashAccount": { "value": "1910" } }

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

Hello, yes, this can be related to the access (User>Company>Tenant Token) Could you please review the following setup for your application ? Getting started with Visma Developer Portal 3.3 Choose the Organization/Company you want to work with 3.4 How to assign “App Store: Integration Administrator Role then generate a token based on that Tenant ID you find in the AppStore.

Dante Cavallin · ‎09-06-2023

Yes but as you saw in my first answer I do use parameters to limit the data scope and it was then I got the error, what I think you should do is to never return 500(Internal server error) error messages out to the API, in this case you should catch these errors on the serverside and reformat the error so that we who use the API can easier figure out for ourself what has gone wrong.

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

Hello Erik, unfortunately this connection described in the UI is not available via the API. I'd recommend you creating an Idea by describing the process steps and corresponding module to be reviewed for implementation to the API.

ReinderReinders · ‎08-06-2023

Thank you, I'll set this as the accepted solution.

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

Release Notes Documentation Fix Version/s Improve performance on GET InventoryTransfer endpoint. We have significantly improved the performance on the InventoryTransfer endpoint. Please give feedback on your experience. 9.50.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 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 Branch filtering for JournalTransaction endpoint to be applied on transaction instead of batch At this moment, the Branch filter on the JournalTransaction endpoint is applied on batch level. It will be switched to be applied on transaction level instead of batch. This change will be enforced starting the 20th of June 2023. The ones willing to switch to this new approach earlier can contact the partners, support, or development team. Jun 20, 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 · ‎07-06-2023

Release Notes Documentation Fix Version/s Performance issues when using the API endpoint "PUT Stocktake V2" The performance of the "PUT Stocktake V2" API endpoint has been improved. For example, 100 lines going from 40.2 seconds to 1.33 seconds. 9.49.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 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 Branch filtering for JournalTransaction endpoint to be applied on transaction instead of batch At this moment, the Branch filter on the JournalTransaction endpoint is applied on batch level. It will be switched to be applied on transaction level instead of batch. This change will be enforced starting the 20th of June 2023. The ones willing to switch to this new approach earlier can contact the partners, support, or development team. Jun 20, 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

KonsultVn · ‎07-06-2023

Thanks! I tried linking the customer to a new invoice directly in the UI and received a more detailed error regarding an invalid zip code. It would be greatly appreciated if in the future you could get this error message out rather than the current "Object reference not set to an instance of an object.". It would have made it a lot easier for us in troubleshooting.

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

Thanks for the confirmation Steffen

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

Hi, currently "LandedCost" tab is not exposed via Supplier Invoice Endpoint. If you'd like to get this DTO extended, please create this in the Ideas sction by specifying the request details (what operation, request flow etc) so that this will be reviewed by the development team. Thanks.

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

"That error "Invalid audience" signals that the access token used on the request has no scopes of the Visma.net ERP Interactive API. On the authorization request, the client needs to include at least one of the API scopes: vismanet_erp_ interactive_api:create, visman et_erp_interactive_api:delete, vismanet_erp_interactive_api: read or vismanet_erp_interactive_ api:update beside the offline_access. "

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

Hello, you can check the document Getting started with Visma Developer Portal > Step 3: Create Your App Store Account

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

Hi, first, you need to figure out what is your ERP company Segment / Number series settings for the "Customer". 1) Segment keys(ScreenId=CS202000&DimensionID=CUSTOMER) 2) Number series (ScreenId=CS201010) If auto-numbering enabled in the UI, but you'd like to override it via API, How to override Visma.net Financials ERP number-series (Automatic) via API Then, regarding reading the number / ID of the recently created object, please see : How to read recently created object ID from Visma.Net API Response Headers ?

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

As far as I remember from the old cases like 3–4 years ago, PaymentMethod endpoint has initially been only for Supplier Payment Methods so that the new CustomerPaymentMethod endpoint has been introduced. However, we'll check the current flow of it, and I'll let you know.

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

Hello, thank you for reporting this, we'll look into that and inform the related team for the clarification.

Re: error in salesorder API creating sales order

[Release Notes] - Visma.Net API 9.53.0 - 27.06.202...

Sv: Timeouts from the InventoryTransfer endpoint

Re: Problem creating supplier payment

Re: invalid_grant when using refresh token

Re: Error updating supplierClassId of Supplier

Re: Strange message on PurchaseOrder update

Re: paymentMethodId for api/v2/customerCreditNote

Re: Error for period when creating SupplierInvoice

[Release Notes] - Visma.Net API 9.52.0 - 20.06.202...

Re: Our account can not add the interactive api in...

Re: Invoice --> Transito field

Svar: Error message when posting Journal Transacti...

Re: SalesOrder V3 Discount problem

Re: Inventory adjustments/issues adding date probl...

Re: Create 'credit note' invoice

Re: 'Access denied' during authorisation through V...

Svar: Error when getting InventoryTransfers using ...

Re: Associate deferred revenue transactions with i...

Re: Forum: Search posts by username doesn't work

[Release Notes] - Visma.Net API 9.50.0 - 06.06.202...

[Release Notes] - Visma.Net API 9.49.0 - 30.05.202...

Re: Customer invoice POST returns "Object referenc...

Svar: API timeout since your upgrade on the 16th o...

Re: Accessing landed costs on a supplier invoice t...

Re: https://integration.visma.net/API/controller/a...

Re: Authentication

Re: POST api/v1/customer Customer created with the...

Re: /api/v1/paymentmethod only returns creditor pa...

Re: API specification is incomplete - where are th...

Useful pages

About Visma

Contact us

Follow us