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
... Vis flere
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.
... Vis flere
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 flere
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 flere
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 flere
.gif "VISMA"){kind=icon}
Visma Danmark
Visma Finland
Visma Letland
Visma Hollland
Visma Norge
Visma Sverige
Visma Developers & Partners
Visma Latinamerika