The bAccountId under customers in SalesPerson return on GET the internalId on a customer and not the customerNumber It would be great to have the customerNumber as well.
... View more
When creating journalTransactions, creating 1 and 1 works fine. However if one tries to be a little more efficent and run it parallel and send 2 or more at the same time, I get errors back when trying to create it.
Errors returned is normally "Base currency is equal to customer currency" of "Sub account can not be null"
If I just wait 1 sec, and run the exact same post, it works
So the preformance of this rutine is not so good .
... View more
That makes no sence. We're creating the invoices through API, så it should be populatet regardles of what module is used. There's to many if and buts where and where not attriutes are populatet. Make it easy for us to use the data, and this is one more example of not makeing it easy. Please make the changes and populate the data so it makes it usable for us.
... View more
The lineType attribute is missing when using GET on CustomerInvoice/{invoiceNo} I also want to have this on POST so this can be used to set individual linerferences or other references from external system. Or an alternativ is to extend the invoiceLine model and add a new field for that kind of usage.
... View more
When getting attributes, https://integration.visma.net/API/controller/api/v1/attribute I expect to get model as described in swagger in return: { "attributeID": "string", "description": "string", "controlType": "Text", "internal": true, "entryMask": "string", "regExp": "string", "details": [ { "valueId": "string", "description": "string", "sortOrder": 0, "disabled": true, "errorInfo": "string", "metadata": { "totalCount": 0, "maxPageSize": 0 } } ], "createdDateTime": "2023-10-09T11:27:19.353Z", "lastModifiedDateTime": "2023-10-09T11:27:19.353Z", "errorInfo": "string", "metadata": { "totalCount": 0, "maxPageSize": 0 } } However that is not the case and both createdDateTime and lastModifiedDateTime is missing
... View more
Where do I retrieve locations set on the Suppliers. https://integration.visma.net/API/controller/api/v1/location only returns for customers.
... View more
It seems like that externalInventoryId is a read only property in the API on the supplierinvoice endpoint. Is that correct? If so, please make it avaliable to set through the API also. This to referense external imported id's and to be used on external reports. screen id AP301000
... View more
The fields under "inleverans" in screenid AP303010 are missing in the output data through the API. I would also like to have 2 extra date fields in the screen "valid from" and "valid through" . This is to be used to filter on dates, automatically activate / in activate or delete locations.
... View more
I have that. Creating new token, works well to create new invoice, read customers, suppliers and more. I can also create the payment, but the action release will not work Still get error 403 - Forbidden message=Scope requirement not met
... View more
When doing a POST https://integration.visma.net/API/controller/api/v1/customerpayment/400013/action/release with body like : { "type": { "Value": "Payment" } } I get error 403 - Forbidden If I just change to the old static token the same request works fine. All scopes are allowed in the app.
... View more
It's urgent. All orders fail on import if one sets this value. Please don't shut down the old endpoint yet. Extend the grace period due to these types of errors. We had rollback to old version of the integration due to this.
... View more
When trying to send salespersonid creating an order in V3, I recieve error 400 - bad request. This Id exists in Vn and works great using the old endpoint. (https://integration.visma.net/API-index/) I've tried with some of the other salespersons, but getting the same error.
... View more
The performance is inconsistent and very slow. Almost 30 sec to create trying the exact same post moments later getting a 503 - service unavaliable
... View more
So the SalesOrder endpoint in v2 will still have some of its functionality after June 1st? And it's only the get/put/post of salesorder that's affected? This meaning that we have to use both salesorder v2 and salesorder v3 in combination?
... View more
When adding new orderlines to a existing salesorder, it seems to require the ETag header also. In the swagger documentation, this is as I can see only this documented on the PATCH /api/v3/SalesOrders/{type}/{orderId}/lines and PATCH /api/v3/SalesOrders/{type}/{orderId} Is this as it should be or should it not be required on POST /api/v3/SalesOrders/{type}/{orderId}/lines (adding new lines to the salesorder)
... View more