About erik-kle

erik-kle · ‎13-12-2023

We encountered this today. The app was installed this morning and now we get Branch '1 ' cannot..... Is there a 24 hour waiting before it works?

erik-kle · ‎21-08-2023

Any updates on this?

erik-kle · ‎21-08-2023

Any updates on this? We have a new customer where this feature is necessary

erik-kle · ‎17-08-2023

Add the possibility to Post attachments to CashTransactions

erik-kle · ‎11-05-2023

What about the new auth? Will that be enforced?

erik-kle · ‎11-05-2023

Ok so there is no fixed date? Have 1/6 been communicated earlier? Because im certain i have heard that date along with the new auth, bur now i cant find any reference to it. So neither new auth or transition to SalesOrder V3 will be enforced for 1/6? Edit: I now found this statement " In the current plan, we will start deprecating the old endpoints in 1st of June 2023." from this page https://community.visma.com/t5/News-in-Developers-Visma-net/Goodbye-salesorder-endpoints-hello-Sales-Order-Service/ba-p/485636

erik-kle · ‎11-05-2023

In communication with a customer where we notified that the auth will be changed and we have to get an app installed to continue with integrations after 1/6, the customer responded that another ISV had told him that the new auth will not be enforced before 31/12 2024. In my understanding 1/6 is the date for enforcing. Is that correct?

erik-kle · ‎31-03-2023

+ 1 We experience the same error for POST Salesorder in v3

erik-kle · ‎27-03-2023

"Connection to cache service failed" 14:30 and 15:30 today controller/api/v1/inventory

erik-kle · ‎28-02-2023

Add Financial Fees for CustomerPayment endpoints POST/PUT/GET

erik-kle · ‎09-01-2023

Why do you have a fauna of different SalesOrder objects for different endpoints? Isnt it possible to define a domain SalesOrder object, that are used for GET, POST, PUT, instead of NewSalesOrderCommand, SalesOrderDto, SalesOrderListDto etc, that are all a bit different.

erik-kle · ‎04-01-2023

Hi, Upon a first glance of the POST v3/SalesOrders i find that ShipVia and ShippingTerms is missing. Will the NewSalesOrderCommand be extended with more fields in the coming months?

erik-kle · ‎22-12-2022

Both shipVia and shipTermsId are crucial for many of our webshop integrations. Will this be available in the NewSalesOrderCommand before closing of v2?

erik-kle · ‎22-12-2022

Allow the possibility to add attributes to more entities in VN, the same as inventory, customer etc. This would provide a greater way to extend and integrate with VN, and to build custom solutions in a more dynamic way. The entities that would benefit from attributes are: SalesOrder SalesOrderLines PurchaseOrder PurchaseOrderLines CustomerInvoice

erik-kle · ‎22-12-2022

/controller/api/v1/customerPayment/{paymentNumber}/action/release

erik-kle · ‎22-12-2022

Expose a way to run generic inquiries as GET in the api. This would allow for a more dynamic way to get data than only fixed endpoints and allow the fetch data that is not available in the api

erik-kle · ‎22-12-2022

GET/controller/api/v1/cashaccount/{accountNumber} Get a specific cash account

erik-kle · ‎31-08-2022

A workaround in multiple live integrations, takes days to implement. This is the 4th consecutive upgrade this summer that introduces breaking bugs. All seems to be releated. Do Visma have a plan for testing so this can be avoided in future updates?

erik-kle · ‎31-08-2022

A customer reports that lineDescription and uom is not posted on SalesOrderV2. So this old bug from this summer is probably back. IPP-REQUEST-ID: 0fa328f1-6b77-4c9a-a0f4-f51c3a73b4af

erik-kle · ‎31-08-2022

A customer reports that lineDescription and uom is not posted. So this bug is probably back. IPP-REQUEST-ID: 0fa328f1-6b77-4c9a-a0f4-f51c3a73b4af

erik-kle · ‎30-08-2022

PUT /controller/api/v1/shipment/{shipmentNbr} 500 - VismaId: 02995599-65ad-411e-93df-ca149b752a13. Object reference not set to an instance of an object { "shipmentNumber": { "Value": "000126" }, "shipmentPackageLines": [ { "boxId": { "Value": "PC" }, "weight": { "Value": 90.000000 }, "customRefNbr2": { "Value": "Test" }, "operation": "Insert" } ] }

erik-kle · ‎22-08-2022

After futher investigation we get corrupt RC orders when creating them in the apit. But in the UI it works. Its not possible to receive, we get an error about no planned lines to receive. Can this be related to the bug (that is in forum thread "Issue posting create shipment on sales order") that was introduced around 15/7 when it was errors on SO shipments not able to create shipments?

erik-kle · ‎22-08-2022

When posting a RC via SalesOrderV2, with negative quantity on one line (for handling return fees) the header summaries shows negative amount. But that doesnt happen if creating an exact copy in the UI. The order cannot be fixed without deleting the lines and adding new ones in the UI. Is this a bug?

erik-kle · ‎10-08-2022

No, the first order with the issue was created 2022-08-09 12:05:26 in the api, and after that all orders have this issue, even orders created now.

erik-kle · ‎10-08-2022

This started yesterday around 15 12 i think. All orders imported after that have ended up on wrong warehouses. So either I or the customers must now allocate time to fix this on every single order. This is the second time this summer that Visma upgrades introduces bugs that are tedious to fix. I cannot charge customers for this.

erik-kle · ‎10-08-2022

We can no longer set warehouse on lines, it defaults to the default for each product. This is validated on two separate customers, and is still an issue. Fix it now!!!!

erik-kle · ‎15-07-2022

This starts to become a big issue now, the amount of orders that we cannot create shipments on is growing fast. When is your fix being deployed?

erik-kle · ‎15-07-2022

.

erik-kle · ‎15-07-2022

One customer reports this error on orders from yesterday (14/7) after the feature was toggled off. Why is that? Have the Visma fix been deployed yet?

erik-kle · ‎13-07-2022

One of my customers reports that on orders, created before the feature was toggled off, shipments cannot be created, the errors consists. What is the fix that we can provide?

Re: Error: Branch '1 ' cannot be found in the ...

Svar: create a customer invoice from a shipment?

Svar: Known issue: Unable to update "componentID" ...

Add attachment to CashTransactions

Svar: Move of breaking change Due date for Sales o...

Re: When will the new auth be enforced?

When will the new auth be enforced?

Svar: SalesOrders v3 - Error 500 on customer, but ...

Re: Urgent - Connection to cache service failed

Add Financial Fees to CustomerPayment

Re: Migration from v2/SalesOrder to v3/SalesOrders...

Migration from v2/SalesOrder to v3/SalesOrders Que...

Svar: nextGen-Api: Posting Salesorder, fields 'shi...

Add attributes to more entities in VN

Allow release of Refunds in CustomerPayment

Expose Generic Inquiries in API

Expose IBAN and BIC on CashAccount

Sv: Errors after Visma update today - Critical

Svar: "You don't have permission to access this re...

Sv: Errors after Visma update today - Critical

Svar: "You don't have permission to access this re...

Svar: Possible bug in Post RC SalesOrderV2

Possible bug in Post RC SalesOrderV2

Svar: Errors after Visma update today - Critical

Svar: Errors after Visma update today - Critical

Svar: Errors after Visma update today - Critical

Re: Issue posting create shipment on sales order

Re: Issue posting create shipment on sales order

Re: Issue posting create shipment on sales order

Re: Issue posting create shipment on sales order

Useful pages

About Visma

Contact us

Follow us