Over Gert-Jan van der Kamp

Oskar Jansson · ‎08-04-2025

Hi @sumo, the purpose of this knowledgebase article is to help API users test the API using Swagger. If you need information about pricing, etc., please visit our webpage: https://www.vismasoftware.no/api-en https://vismasoftware.se/api https://www.vismasoftware.no/api

Marten Voort · ‎27-01-2025

Thx for the update Gert-Jan!

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?

Trygve Storrønningen1 · ‎25-10-2024

Visma, this topic is hot. And important. Relevant ideas and questions: * https://community.visma.com/t5/Ideas-in-Developers-Visma-net/filtering-on-salesorders-endpoint-missing-this-is-showstopper-to/idi-p/689571 * https://community.visma.com/t5/Forum-in-Developers-Visma-net/Filter-orders-on-min-and-max-date-SalesOrder-API-v3/m-p/690887

Gert-Jan van der Kamp · ‎08-07-2024

Hi, I'm getting a 500 error when trying to create a PurchaseOrder, is there any way I can see more details for this VismaId like with the Connect debugger? This doesn't provide much detail how to fix the error. Error: HTTP 500 : InternalServerError {"message":"VismaId: ed8061a0-eda8-4b19-8e8e-29177a5f5d7b. Error creating purchaseOrder. Object reference not set to an instance of an object."} at http (C:\Users\Gert-JanvanderKamp\source\modules\http.js:38:48) -> let res = xlc.http(verb, uri, j, hds, auth).Result at Script [131] [temp]:9:15

Gert-Jan van der Kamp · ‎21-06-2024

Also tried adding publicId when creating the segment but that gets ignored.

Gert-Jan van der Kamp · ‎20-06-2024

Sorry never mind must have been cross-eyed yesterday night I see the ETag now. Can;t delete this post.

Marten Voort · ‎21-05-2024

Hi Gert-Jan, you are right, attributes are not part of the POST/PUT Project dto. We have registered a wish for this quite some time ago, but due to few requests this is still on backlog. At this time this is only possible by UI or import scenario. I hope this might form a viable workaround for your case.

Gert-Jan van der Kamp · ‎13-05-2024

Hi we just started having this issue again. We'll wait for it to pass but hopefully you can see something in the logs on why this happens? Client id is isv_xlconnect. Rgds Gert-Jan

Marten Voort · ‎25-04-2024

Hi Gert-Jan, glad it works now! Yes the PK also contains the lineNbr, together with the stockitem and revisionID. This can be a bit trial and error sometimes, but the provided example in https://integration.visma.net/API-index/ should always work or give a meaningful error message.

Yıldırım · ‎02-01-2024

Hi Gert, this module indeed is not available via the API at the moment. This can be registered in the Ideas section of the community so that this can be reviewed for the implementation.

Gert-Jan van der Kamp · ‎07-09-2023

Prefect thx!

Gert-Jan van der Kamp · ‎17-08-2023

Never mind, I'll delete the clip itself on loom

Yıldırım · ‎23-06-2023

Hello, could you please report this to channel: VNI-Support@visma.com including developersupport@visma.com in the cc ? Thanks.

Yıldırım · ‎20-04-2023

Hi Gert, I'll investigate this in detail and get back to you.

Yıldırım · ‎02-03-2023

In documentation 3.5 Find & Approve the integration for the Organization/Company > 1

Yıldırım · ‎27-02-2023

Hello Gert, no problem, we understand that. Could you please contact us via developersupport@visma.com sharing your application name & Client ID so that we can figure out the details that you need information. Thanks.

Gert-Jan van der Kamp · ‎14-12-2022

Ok too bad. You might want to take an existing dataset and anonymize it, it's a lot of work for partners to create such a dataset to be able to test properly. Much easier to do that only once.

Gert-Jan van der Kamp · ‎09-11-2022

Hi apologies for the late reply, I couldn't post to the forum. I setup an app registration isv_xlconnect in the developer portal, it's Native app with PKCE and OpenID Connect. Then use this code with IdentityModel to get the cookie: var options = new OidcClientOptions() { Authority = "https://connect.visma.com", ClientId = "isv_xlconnect", Scope = "openid email profile offline_access", RedirectUri = "http://localhost:8888/callback/" }; That all works fine, it returns a webtoken. But the call to the api abobe fail with the message. One thing I can see is that the applictation regsitration I made in the dev portal uses as https://connect.visma.com authority, while the api uses https://signin.visma.net/ when I click authorize on the Swagger Docs. Could that be the issue?