Thx for the update Gert-Jan! ... Meer weergeven

Hi Kanyar, I have additional information and a timeframe regarding this topic. This functionality is planned to be available in the SalesOrder API by the end of this week. It will work in the following way: if you select "Hold document on failed credit check" in the order type and create an order where the credit verification is triggered (for example, if the credit limit is exceeded), the order will be created, but the status will be set to "Credit hold." As a result, actions like shipment cannot be made for the order.   Information about this will be published in the Release Notes of Sales Order Service API in the near future. ... Meer weergeven

Hi,   Thanks for your answer.  We have acutally implemented something close to what you describe and has not had any missed entities since then, so hopefully that will take care of the problem. Its not the cleanest solution, but it works.    We can leave it at that and if we should experience further issues with this I will reach out again.   Thanks ... Meer weergeven

Still no luck with this. I was told to add Visma.net ERP Service API to my applications, which I did, and it is approved. Now, when trying to read customer, I'm getting Bad Request trying to connect https://connect.visma.com/connect/token - using same params as with salesorder api except scope. Any ideas? ... Meer weergeven

Thanks for the information! I have tried this with different data, now for 10 lines, this worked also with your method. Considering this would need more in-depth research of the detailed environment, I suggest to seek advice from your country specific support. They can guide you in more in depth detail. Please see https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710 ... Meer weergeven

Hi Johan, I suspect this is changed due to the expansion of the SalesOrders v3 endpoints. This information is now available under the shipment endpoint. See /api/v3/SalesOrders/{type}/{orderId}/shipment. Let us know if this information answers your question. ... Meer weergeven

Also requested for: projecttask accountgroup ... Meer weergeven

Thank you for the information! To thoroughly investigate this issue, we need to examine the details involved. As this may require reviewing the company-specific configuration, I recommend reaching out to the support teams specific to your country. Please see https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710. ... Meer weergeven

I checked again, and it works! Did not see it first because of a delay. Thanks for fixing this!  ... Meer weergeven

Hi Gert-Jan, for a given bank account you can only use the currency set in that account. In your request I see cash account 20080. The application currency will always be in the currency of this cash account. In the UI this field is not editable. Can you check what the currency is? ... Meer weergeven

Any update on this? ... Meer weergeven

Hello, The request worked properly in Postman. I have no idea why the same request does not work from azure logic app. I made a work around through an azure function and that works.   Best regards, Magnus ... Meer weergeven

Yes, i know that but it doesn't scale. ... Meer weergeven

Hi! This has now been solved, "overrideNumberSeries" has been introduced in POST salesOrders   https://community.visma.com/t5/News-in-Developers-Visma-net/Release-Notes-Sales-Order-Service-API-1-1-0-1185/ba-p/692324 ... Meer weergeven

Not yet Sierd, I will investigate and come back to you. ... Meer weergeven

Thanks for the information. You are trying to set up a subscription from Visma net trhough the developer portal. This can function as a dispatcher, but then the publisher also has to be set up. It would be easier to directly use Visma net's webhooks. You can read more about this here https://community.visma.com/t5/Knowledge-base-in-Developers/Visma-net-ERP-API-Webhooks-Setup-API-amp-ERP-UI-Event/ta-p/269390 If this does not answer your question let us know. ... Meer weergeven

Terzijde: Invantive is implementatiepartner. ... Meer weergeven

There is an option to use auto-numbering, in that case the invoicenumber is different from the number you POST in the initial invoice request (which is ignored then). But in your case the number seems to be the same, so that is good. The problem is that the invoice has the status balanced, which is a concept state. After you have released the invoice it should be able to be paid. ... Meer weergeven

Ok, then one of your segmentvalues your are posting does not exist in the company, could you check that? ... Meer weergeven

Hi Anton, this might be related to salesorders being edited while you are creating the shipment. Can it be created in a second attempt? ... Meer weergeven

Hi Adrian,   Thanks for you input. Unfortenately I can't keep a client secret secured, that why I use a native app. Still think that the expiration period of a refresh token should be sliding since last use instead compared to the first user consent.   Best regards, Sander     ... Meer weergeven

It is difficult to assess if the current configuration interferes with the test site. Taking into consideration that we would have to study this case in more detail and in its surroundings like ERP company, app settings etc, it would be best if you contact our country-specific support. Please find the contact methods in this link https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710 ... Meer weergeven

Do you have any idea why it works when we test on Companies in ISV Boardeaser AB but not for our customers? When I go through the same flow as a customer: 1. Sign in to Boardeaser 2. Click on our generated authorize link ( https://connect.visma.com/connect/authorize?client_id=isv_boardeaser&redirect_uri=https%3A%2F%2Fapp.boardeaser.com%2Fintegrations%2Fvisma_net&response_type=code&scope=vismanet_erp_interactive_api%3Aread&state=state) 3. I sign in to Visma.net 4. I select `Visualby Test Company` 5. It redirects to Boardeaser 6. We request a token ( https://connect.visma.com/connect/token) 7. The account is connected. But for our customer it fails on step 6 and we get `invalid_request` as the error message with status 400. The API call for step 6 is as follows: POST https://connect.visma.com/connect/token code=valid_code&grant_type=authorization_code&redirect_uri=https%3A%2F%2Fapp.boardeaser.com%2Fintegrations%2Fvisma_net&client_id=isv_boardeaser&client_secret=fake_secret headers: {"Accept"=>"*/*", "User-Agent"=>"rest-client/2.1.0 (darwin23 arm64) ruby/3.3.1p55", "Content-Type"=>"application/x-www-form-urlencoded", "Content-Length"=>"150", "Accept-Encoding"=>"gzip;q=1.0,deflate;q=0.6,identity;q=0.3", "Host"=>"connect.visma.com" response status: 400 body: {"error":"invalid_request"} ... Meer weergeven

Hi! A credit write-off is an internal document used to write-off a credit note. It can only exist when applied to a credit note and cannot be printed as a document. Therefore from an API request you will not receive an address in the response. In UI it is only there because it is opened from the invoice screen with standard layout.   In the endpoint documentation the expandInvoiceAddress is there because this is part of the standard customerdocument, just like there is dunningLetterDateTime for example. These fields serve no purpose for this type of document.   Can you elaborate why you would need an address from this documenttype? ... Meer weergeven