About Marten Voort

Marten Voort · ‎27-01-2025

Thx for the update Gert-Jan!

Marten Voort · ‎30-12-2024

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

Marten Voort · ‎30-12-2024

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.

Marten Voort · ‎30-12-2024

Hi Marcus! Thx for your elaborate explanation. I have tested this and in my test with only a couple of purchase invoices I had no problems fetching very recently created invoices. I suspect when creating multiple transactions simultaneously, the system needs time to process and can only store the values once creation is successful. This is hard to prevent, because in case of an error or disruption of the service, a rollback must be performed. I have seen similar integrations that solved this using the MAX value of lastModifiedDateTime of the previous request result to perform the next request. Could this also apply for your process?

Marten Voort · ‎24-12-2024

Also requested for: projecttask accountgroup

Marten Voort · ‎18-12-2024

Hm this should work, in this case I suggest to seek advice from your country specific support. They can guide you in more in depth detail https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710

Marten Voort · ‎18-12-2024

Thank you for the information. I have used your script and were able to update the invoice without problems. Can you describe the precise steps to reproduce this problem?

Marten Voort · ‎18-12-2024

Hi Jukka, Is the scope added to you app? You should enable the scope AND use it in the authorization request to be able to use it.

Marten Voort · ‎11-12-2024

You should use https://integration.visma.net/API/controller/api/v1/customer to get the right result. Can you try this?

Marten Voort · ‎11-12-2024

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.

Marten Voort · ‎11-12-2024

Hi Jukka, unfortunately this field is not available. If you need to update customers based on changes, you can use Visma net generic API https://integration.visma.net/API-index/ or use webhooks. Let us know if this answers your question.

Marten Voort · ‎09-12-2024

Hi! When you experience this error in the API, is it possible to manually select the transferorder in the UI?

Marten Voort · ‎09-12-2024

Hi Charlotte! Unfortunately we do not see a JSON payload or attached screenshots. Can you add these? Thx in advance 🙂

Marten Voort · ‎26-11-2024

Hi Daniel, thx! I just tested this, using an invitation code, deleting and adding both trigger webhooks for me, see screenshot. Have you enabled the Idp scopes?

Marten Voort · ‎25-11-2024

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?

Marten Voort · ‎06-11-2024

I am referring to the GET request to retrieve the status. If you are not doing any GET requests that could not be it. There has not been a code change. I have tested this endpoint and it accepts all background operations without any complaints. I advice you to test this from an isolated client, like Postman, to clarify what the issue could be. If that does not help, more in depth investigation is needed. In that case I advise you to contact country specific support https://community.visma.com/t5/Forum-in-Developers-Visma-net/Update-on-Visma-net-ERP-API-Support-channels/m-p/633804#M4710

Marten Voort · ‎04-11-2024

Hi, this should work now, can you verify?

Marten Voort · ‎04-11-2024

Hi Magnus, from what I see in the logging I suspect you are also using the erp-api-background header in the status retrieval GET request, hence the 400. Could you check? Thanks in advance!

Marten Voort · ‎31-10-2024

Hi! In this situation it is best to first check if it is possible to create an invoice manually, if that does not work, there will be a more informing error message. Otherwise more investigation is needed.

Marten Voort · ‎23-10-2024

Hi zimplydaniel, we are investigating this and will come back to you as soon as possible.

Marten Voort · ‎08-10-2024

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

Marten Voort · ‎30-09-2024

In the next release (version 10.20) this problem is solved. Let us know if the situation still occurs.

Marten Voort · ‎25-09-2024

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.

Marten Voort · ‎24-09-2024

Our development team has pinpointed the issue causing this particular behavior. A solution is now being tested, and findings look promising. We'll keep you posted as we progress. Thank you for your patience and understanding.

Marten Voort · ‎23-09-2024

Hi Erik! Thx for your post, I have analysed this and was able to reproduce the scenario. I have reported this internally and will come back to you when I have more information.

Marten Voort · ‎18-09-2024

Please see comments in response to kashyap's question 😉

Marten Voort · ‎18-09-2024

This is not possible unfortunately, you have to do two separate requests to to get this desired effect.

Marten Voort · ‎17-09-2024

Hi! All lastModifiedDateTime fields in the child objects of the Inventory endpoint relate to changes in availability. Not te be confused with actual item-warehouse details for example. Therefore you will find them directly below available fields in the endpoint response. These can also be filtered when executing a GET request. You can use the parameters availabilityLastModifiedDateTime and availabilityLastModifiedDateTimeCondition to activate this filter. Let me know if this has the desired effect.

Marten Voort · ‎12-09-2024

Planned start date: Sep 18th 2024, 01:00 CEST Planned end date: Sep 18th 2024, 04:30 CEST Expected downtime for Visma net ERP and Visma net API. Status can be followed at: https://status.visma.com/incidents/3ycfqc298y65 A downtime release update has been planned for Visma net ERP in this timeframe, so we ask you to plan your integrations accordingly. We apologize for any inconvenience this may cause. Thank you for your understanding.