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 ... View more

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 ... View more

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. ... View more

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...? ... View more

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. ... View more

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) ... View more

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. ... View more

Visma, are you still around? 😉 ... View more

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. ... View more

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. ... View more

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

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

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? ... View more

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... ... View more

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. ... View more

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

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

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. ... View more

When posting with a valid inventoryId but invalid orderType (eg. ROK) - I get a short reponse message as expected ... View more

I am now reproducing the big stack trace in Postman by posting an invalid inventoryId POST https://integration.visma.net/API/controller/api/v2/salesorder     ... View more

Yes, but I am not sure the reason of failure is effecting the problem with big stack trace. It seems also Florian got the big stack trace with different situation/error.   I am neither able to reproduce this with simple calls from Postman, but we do get this in the error response stream when calling from code. I think it might be  ... View more

We are also now receiving a big stacktrace when receiving a 400 Bad request. I asume this is by a glitch. But it should be considered a security glitch as well - as it could contain information you would not want to show to an outsider.    In our case we sent an order with a orderType not existing in Visma.net - which of course absolutely SHOULD fail - as it does, but we received this error message: {"message":"VismaId: 54ce7920-e8cd-43d3-90ff-a4f560976a53. Error creating salesOrder. System.Reflection.TargetInvocationException: Exception has been thrown by the target of an invocation. ---> PX.Data.PXSetPropertyException: The specified inventory ID or alternate ID cannot be found in the system.\r\n at PX.Data.PXSelectorAttribute.throwNoItem(String[] restricted, Boolean external, Object value)\r\n at PX.Data.PXSelectorAttribute.SubstituteKeyFieldUpdating(PXCache sender, PXFieldUpdatingEventArgs e)\r\n at PX.Data.PXDimensionSelectorAttribute.FieldUpdating(PXCache sender, PXFieldUpdatingEventArgs e)\r\n at PX.Objects.IN.CrossItemAttribute.FieldUpdating(PXCache sender, PXFieldUpdatingEventArgs e) in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Pure\\PX.Objects\\IN\\Descriptor\\Attribute.cs:line 8157\r\n at PX.Data.PXCache.OnFieldUpdating(String name, Object row, Object& newValue)\r\n at PX.Data.PXCache`1.SetValueExt(Object data, String fieldName, Object value)\r\n --- End of inner exception stack trace ---\r\n at Visma.net.ERP.Api.Base.BaseDomain.HandleChildCommand(IBaseCommand cmd, Boolean handleChildCommands) in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Api\\Base\\BaseDomain.cs:line 72\r\n at Visma.net.ERP.Api.Base.BaseDomain.ApplyChildCommands(IEnumerable`1 childCommands, Boolean handleChildCommands) in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Api\\Base\\BaseDomain.cs:line 44\r\n at Visma.net.ERP.Api.SO.CommandModel.SoCommandHandler.Handle_V2(ICreateSalesOrderCommand[] cmdList) in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Api\\SO\\CommandModel\\SoCommandHandler.cs:line 83\r\n at Visma.net.ERP.Web.Api.Repositories.SOOrderWebRepository.CreateSaleOrderReturnSaleOrderNumber(SalesOrderUpdateDto salesOrderUpdateDto, String orderType, Int32 version) in D:\\Data\\BuildAgent\\work\\11023e52ea15d342\\Web\\Lib\\Visma.net.ERP.Web.Api\\Repositories\\SOOrderWebRepository.cs:line 178\r\nThe specified inventory ID or alternate ID cannot be found in the system."} ... View more