About Trygve Storrønningen1

Trygve Storrønningen1 · ‎17-02-2025

Will this URL replace both: https://integration.visma.net/API/ and https://salesorder.visma.net/api/v3 ?

Trygve Storrønningen1 · ‎25-10-2024

Visma, this topic is hot. And important. Relevant ideas and questions: * https://community.visma.com/t5/Ideas-in-Developers-Visma-net/filtering-on-salesorders-endpoint-missing-this-is-showstopper-to/idi-p/689571 * https://community.visma.com/t5/Forum-in-Developers-Visma-net/Filter-orders-on-min-and-max-date-SalesOrder-API-v3/m-p/690887

Trygve Storrønningen1 · ‎25-10-2024

This is not possible now. Feel free to "vote" for this solution for it in ideas 🙂 https://community.visma.com/t5/Ideas-in-Developers-Visma-net/filtering-on-salesorders-endpoint-missing-this-is-showstopper-to/idi-p/689571 This covers the same: https://community.visma.com/t5/Ideas-in-Developers-Visma-net/Expose-Generic-Inquiries-in-API/idi-p/546347

Trygve Storrønningen1 · ‎18-10-2024

This wish/idea also applies to /api/v3/SalesOrders

Trygve Storrønningen1 · ‎18-10-2024

This also applies for /api/v3/SalesOrders

Trygve Storrønningen1 · ‎18-10-2024

We are implementing full MyPage for our solutions with Visma.net - and lookup of orders are of course important on /api/v3/SalesOrders My colleagues ask me about filtering; and I realize now we miss the ability to search for orders or ranges of orders in a good way. What data we have to lookup, can vary, and I think an approach better for both you and ISVs would be an oData-like $filter= It could be we wish to lookup orders created in spesifice time range, of different types, with some special reference, for one customer etc In the near future it would also be important to be able to search after orders with specific details (eg. products) on orderLines, combined with filter on orderhead

Trygve Storrønningen1 · ‎16-10-2023

Hi Joni, for stock import from inventory V3 we also need the filters availabilityLastModifiedDateTime and availabilityLastModifiedDateTimeCondition implemented. This is from this case: https://community.visma.com/t5/Forum-in-Developers-Visma-net/SO-V3-inventory-availabilityLastModifiedDateTime/td-p/595686

Trygve Storrønningen1 · ‎12-10-2023

When we get action/createShipment on V3, we will be able to move more customers to V3. We also need clearification on policy for how breaking changes will be introduced/handled in V3 from now till dec 2024

Trygve Storrønningen1 · ‎18-09-2023

Hi, any news on this? This is high priority for us to be able to offer our customers more updated stock, without spamming your API with frequent requests returning big amount of data.

Trygve Storrønningen1 · ‎07-08-2023

Hi, for stock import from inventory V3 we need the filters availabilityLastModifiedDateTime and availabilityLastModifiedDateTimeCondition implemented. Are there any plans for when it will be implemented? Is it on the list?

Trygve Storrønningen1 · ‎11-05-2023

We started to lift all customers to v3, also using the new auth. What expectations could we have to the stability in v3 till 30th June 2024 - how moving/breaking will it be? Breaking changes in prod for customers... do the math... I am really not certain what do to; roll all customers back to v2 and stay there till 30th June 2024, or take a chance and continue on v3.... Visma, what do you suggest...?

Trygve Storrønningen1 · ‎11-05-2023

Joni, sorry, seems the validation fix is already out there, and the reason for different answers described in last post is -- time. Still, we need for our use case to be able to write this information in a place on the order where other partners can find and use this later in order and payment process.

Trygve Storrønningen1 · ‎11-05-2023

Hi, this could be an option, but it does not really fit the use case. This process is vetted also with other partners as ZData, we agreed on a total good flow for orders and payment for the customers. We would not want to change this now; if it is not to something better -- and I think for us to do other partners work is not where we want to go. It also seems that in some cases we get an error from V3 when we send paymentRef, "Payment Ref is not editable for order type WO" and sometimes we get 201, but no idea where paymentRef goes as it is not to be found in UI. So; what can be the reason for this variation, and when can we be able to add this info to the salesOrder? (as we did before, and as we do with Visma Business, Visma Global, Microsoft ERP, SAP, Tripletex and others)

Trygve Storrønningen1 · ‎09-05-2023

Hi. For a webshop use case, we also do payment, cc, Klarna, vipps etc. We need to be able to write the paymentRef to the order for several purposes: - to identify and to be able to do capture on the order when goods are shipped - to settle accounts when payment bundles are received to identify which order a sub-payment are connected to. Because of this we need to be able to write paymentRef also on SO-based orders.

Trygve Storrønningen1 · ‎08-05-2023

Visma, are you still around? 😉

Trygve Storrønningen1 · ‎02-05-2023

Hi, we are creating an order with his JSON: { "date": "2023-04-27T12:04:00.0000Z", "type": "WO", "description": "Web order nr. web-10018", "shipping": { "shipSeparately": true }, "paymentSettings": { "paymentRef": "11789-web-10018" }, "customer": { "id": "11789", "order": "web-10018", "refNo": "Test test" }, "address": { "postalCode": "2345", "city": "\u00c5DALSBRUK", "countryId": "NO" }, "billing": { "address": { "postalCode": "2345", "city": "\u00c5DALSBRUK", "countryId": "NO" } }, "orderLines": [ { "inventoryId": "200141", "quantity": 1.0, "description": "Test sales product", "unitPrice": 690.0, "hasManualDiscount": false }, { "inventoryId": "Frakt", "unitPrice": 295.0, "quantity": 1 } ] } I get 201 and the order is created. But. We cannot find the paymentRef anywhere on the order in UI. What are we missing?

Trygve Storrønningen1 · ‎13-04-2023

Visma Global supports multiple levels for pacage/bundels. Visma.net currently supports only one level (IN209500) How are the plans/possibilities for extending in Visma.net to support mulitple levels as in Visma Global. This can be important for Visma Global customers considering migrating to Visma.net

Trygve Storrønningen1 · ‎14-03-2023

Hi, Joni! In principle this sounds like a good idea. Are you also suggesting that the order will be given an initial status which indicates that it is valid and acknowledged by the system, which then changes to another status which indicates that the inventory is updated with the quantities in this order? We should be able to tell by looking at the order status whether it is included in the inventory or not. Then it won't matter if it takes a couple of seconds before the separate process completes. In short, the system must tell the truth at all times.

Trygve Storrønningen1 · ‎16-02-2023

Don't know why, but had to manually delete records for integrations.visma.net from the sqlite cookies file in AppData\Local\Microsoft\Edge\User Data\Default\Network Now Issue 2 is working on both Chrome and Edge.

Trygve Storrønningen1 · ‎16-02-2023

Thank you 🙂 Removing cookies solved it in Chrome, not in Edge. And I miss response from Visma here.

Trygve Storrønningen1 · ‎16-02-2023

Visma, any news on this? It was posted 6 days ago, and we also experience Issue 2.

Trygve Storrønningen1 · ‎15-02-2023

Sorry, my bad. For v3; I had scope visma.net.erp.salesorder:write when generating token I missed scope vismanet_erp_service_api:create needed for creating orders in v2.

Trygve Storrønningen1 · ‎15-02-2023

When the v1 and v2 salesorder endpoints are removed June 1st this year, alle Visma customers integrated with these will need to have their integrations rewritten to use v3. We are in the process of this with all Visma.net integrated customers. We as partners and ISVs read all release noted carefully 😉 But pretty sure customers are not. What are Vismas plan for communicating this change with all affected Visma.net customers?

Trygve Storrønningen1 · ‎15-02-2023

We are using the new authentication, and it is working well with same token for: POST v3/salesOrders GET v3/Inventory?inventoryId=p-003&expand=all GET v3/SalesOrders/WO/000067 GET v1/salesorder/WO/000067 GET v1/inventory But with POST v2/salesorder and still same token we get: "message": "Scope requirement not met" The JSON posted is testet ok with the old VNI authentication. I thought scope was for the token, and not dependent on endpoint? Something missing in our setup, or in v2/salesorder endpoint?

Trygve Storrønningen1 · ‎15-02-2023

Will the structure of the JSON response be the same for all V3 endpoints and error situations, with details, errors, title, stauts, detail and instance?

Trygve Storrønningen1 · ‎20-01-2023

Should we be able to read the release notes here? Because when I click the link Release-notes-SalesOrderServiceAPI I return to the list over articles with release-notes. And so the circle goes into the next round...

Trygve Storrønningen1 · ‎08-12-2022

We are using both APIs from same solution - now with same authentication on both - all tests are good so far. integration for v1 and v2 - and salesorder for v3. Inventory and Customers as basic entities are as before GET from v1, salesorder POST to v3. For stock, chose either inventorySummary on v1 or inventory v3. We see no need to duplicate endpoints if nothing else is changed.

Trygve Storrønningen1 · ‎24-10-2022

From our point of view, this should both by legally, security and practically means be the customers. Trygve, Gurusoft

Trygve Storrønningen1 · ‎07-06-2022

Still same both in Postman and code. Salesorder is our biggest headache now 😉 Sorry if messing up this thread 🙂

Trygve Storrønningen1 · ‎07-06-2022

Hi Magnus, I miss response on my answers here. The change in API giving now the big stack trace instead of the correct short message as earlier, is forcing us to temporary roll out a fix for this to all customers so they can get a decent feedback on what went wrong. This should not be necessary. And a dirty fix for temporary dirty data is not of the good.

Sv: Important: End of VNI and transition to Azure ...

Sv: Expose Generic Inquiries in API

Sv: Filter orders on min and max date (SalesOrder ...

Sv: Add attributes to more entities in VN

Sv: POST/GET attributes to SalesOrder / SalesOrder...

filtering on salesorders endpoint missing - this i...

Re: Missing field and actions SalesOrder API V3

Re: Missing field and actions SalesOrder API V3

Re: SO V3 inventory - availabilityLastModifiedDate...

SO V3 inventory - availabilityLastModifiedDateTime

Sv: Move of breaking change Due date for Sales ord...

Sv: paymentRef in V3

Sv: paymentRef in V3

Re: paymentRef in V3

Sv: paymentRef in V3

paymentRef in V3

Multi-levels for package/bundles

Sv: Feedback wanted: Sales order API v3 - eventual...

Sv: Swagger broken since approximately February 2.

Sv: Swagger broken since approximately February 2.

Sv: Swagger broken since approximately February 2.

Sv: POST v2/salesOrder with Visma Connect Authenti...

Removal of salesorder endpoints June 1st

POST v2/salesOrder with Visma Connect Authenticati...

Sv: Error response in Visma.net ERP NeXtGen Sales ...

Sv: [Release Notes] - Sales Order Service API 1.0....

Re: Sales Order Api Inventory

Sv: Ownership of integration users

Sv: Exception when filtering on customes with attr...

Sv: Exception when filtering on customes with attr...

Useful pages

About Visma

Contact us

Follow us