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 ... Vis mer

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.  ... Vis mer

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.  ... Vis mer

Thank you Gert-Jan. It seems like we do need a new license. Strange how none of the docs seem to mention it.   For a Service call, the docs say I don't need a user or a role, but the license seems likely. Thanks again. ... Vis mer

Prefect thx!  ... Vis mer

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

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

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

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.  ... Vis mer

Yes this would allow the query to be defined and executed on the server. We'd prefer to do it this way, now it takes many different calls that need to be combined on the client.  ... Vis mer

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.  ... Vis mer

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?    ... Vis mer