Hi Oskar,   no, the problem was solved after we escalated it internally in Visma in the weekend. We could not wait until today since the whole integration platform stopped. I think somebody in the connect team knows exactly what happened, but I think it was due to a lot of token traffic from our side after the API got to live again. But we have to find out how we can quick enough answers when all is stopping due to such incidents also during a weekend.   Florian ... Mostrar más

@Magnus Johnsen Does this apply for the salesorder /api/v1/salesorder andpoint as well?  ... Mostrar más

Fantastic - you are right. Switching the App-Serviceplans fixed the problem. Thank you for helping! ... Mostrar más

https://integration.visma.net/API-index/#/ is the correct URL for the Swagger UI. It might not work (my issue) if you are logged into the Visma VPN (Cisco AnyConnect I think). ... Mostrar más

The problem is back since about 15 minutes ago... Can you look into it as soon as possible?   ... Mostrar más

We are using ngrok a lot. This also has a web-interface and a great way to see if the webhook is triggered and also the payload of the webhook message.   Florian ... Mostrar más

Hi Magnus   what is the status here? We have still the same issue...   Florian ... Mostrar más

Hi, This is the documentation for the approvals API: https://approval.visma. net/apidocs/configurationapi/ ... Mostrar más

Hi Florian,    please make sure that the new user have the mentioned roles before generating the token (Connecting your Visma.Net Financials company to the API) ... Mostrar más

This does not look like a companyID, could you please doublecheck? ... Mostrar más

The solution to the issue has been found and is planned to be released in version 9.08 currently planned to be released on 2022-08-02 ... Mostrar más

I did the same test now and it seems to be working as it should and using the correct sales account. I am not able to reproduce the same error,  so I believe that this case is not relevant anymore. Maybe Florian still has the same problem?   ... Mostrar más

I still get this error almost every day.     ... Mostrar más

ok, I do so.     ... Mostrar más

Hi,  JSON, Print screens etc. that contains sensitive information can be sent to [email protected]   We'll try to configure the same setup as you have in the integration company to reproduce the issue so that this can be addressed, therefore please send us the settings of the Customer / Company when you've received the error.    1) What are the enabled validations ? Countries/counties/postcodes (ScreenID=CS20400S) Address 1 : ?  Postcode : ✔️ City: ? Email : ? 1.1) Please specify in the email if any "Postcode & City" defined and one of them used in the  "Customer" card that you got error when the validation was active.   2) Customer Card Financials ERP UI  (Send us a print screen for each tab following where we can clearly see the fields)   General information > Main address Invoicing settings > Invoice address Delivery settings > Shipping address 3) Include used POST Sales Order JSON   Thanks. ... Mostrar más

Hello Florian,  this case has been resolved but not released yet. Since it is a breaking change, we've shared the notice period and information about the planned date. Details can be seen here [Due dates for breaking changes]. ... Mostrar más

@Florian Haase wrote: First we thought that the minor part of agreements is based on item-connections (instead of item-group), but now I see thats actually the major part. That means nearly each inventory-item has any connection to one or more of the agreements. Since we need the External InventoryID (stored in the attributes on the inventory-Items) I run a get call now on each involved inventory-Item to get the external ID. (we get each inventory just once even it is used on several discount agreements since we store the result in the memory and reuse it). That causes in the end  an overflow in max number of requests (at least in some situations).   It seams to be better to get the whole inventory database from Visma.Net first with some fewer calls. We did not do this by design first, because the inventory endpoint is so extremly slow but that would of course reduce the number of calls. We will get some more inventories than needed but that's maybe the only way to get around the problem? If the External-ID is static once the discount setup is done, storing all the historical data in your end would be definitely more efficient. In this way you can fetch the new records with "createdDateTime" or "lastmodifieddatetime" filters targeting to retrieve new inventories or only if there are any changes on the item.    Alternatively, you can check the New Sales Order API Service that GET-Inventory Endpoint is available and should perform better.  <https://salesorder.visma.net/swagger/index.html>   Should return the inventory with the attribute values assigned. https://salesorder.visma.net/api/v3/Inventory?expand=Attribute   Getting started with the first neXtGen service: Visma.net ERP Sales Order API ... Mostrar más

We're experiencing the same issue across several customers / companies ... Mostrar más

I think you are right, but I don't find the change in our integration either. But we deserialize the json and serialize it again before we forward it. Maybe something in the JsonConverter has changed and it handles the enum in a different way... FLorian ... Mostrar más

Hello,  we've confirmed that the fix will be implemented as SalesPerson V2 Endpoint.  The rest (Discount / DiscountCode) will also be assessed in this way.  ... Mostrar más

Hi, We'll have a look at this and get back to you. ... Mostrar más

We've identified that undocumented Swagger Change released with Visma.net Financials ERP 8.55 version (29-06-2021) has caused an issue with some endpoints. For further information, please subscribe to: Known Issue: Some Endpoints started to return "Bad request for URI" error after 8.55 version   ... Mostrar más

Thanks for the confirmation Florian 😊 ... Mostrar más

Don't need it today 🙂 The workaround works for us but causes a bit traffic on the API because we have to read the inventory and afterwards we have to read the subaccount for each line (not implemented yet) ... Mostrar más