Hi Tapiiri, thanks for the information. We'll check it out and get back to you.  ... View more

Hello, this should be related to the Application & Authentication type. Unfortunately , currently there is no way to combine both auths in a single application.  Since there is no user assigned for the service API, it retrieves the ClientID, however that's not the case with the with interactive.  ... View more

Hello, we'll review this and get back to you.  ... View more

Hello Johan,    1) Unfortunately we don't have a timeline revealed for the unification process at the moment, however we're doing our best to handle it as soon as possible.    2) Because currently they're using different authentication bases due to endpoint structures and their dependencies according to ERP UI rights. For sure this can be changed in the future, we'll keep the community updated if there are any plans.  ... View more

If it's only the first request, then I'd recommend debugging the payload to see what values constructed in the payload for the first object created from the excel data.  ... View more

Hello,    All functionality currently missing in the new Sales Order Service API has been planned to be added before removing the old endpoints.  ... View more

Hello, we'll investigate it and get back to you with information asap. ... View more

Hello,    currently, the new Sales Order Service API is not including all the features exposed via the legacy Sales Order Endpoint. We don't have a field to field map between old and new DTOs however the field definitions of the new service can be seen at https://salesorder.visma.net/swagger/index.html    Getting started with the first neXtGen service: Visma.net ERP Sales Order API   Please let us know what information you're missing in detail, so we can check it out for you.  Thanks.   ... View more

Thanks Gabriel, we'll keep you informed on the progress and the release details.  ... View more

Hello,    please create an "idea" for exposing those fields, including a print screen from the module highlighting the fields/operations in detail. Thanks. ... View more

Hi,  if you could specify the report / module / process etc name that is used for fetching bank account balances in the Financials ERP UI by the customer, we can check it out for the API.    Thanks. ... View more

Hei Steinar, thanks for the info ! Please let us know if you experience the same issue again, then we can look into that together.  ... View more

Hello, you can try sending the payload without cash account to see what default value it gets.  ... View more

Hei,    have you inspected batches 002612 & 002507 in detail ? What are the values assigned,  what is the reference connection between the invoice and the journal transaction ?  ... View more

Hello !    Since batch numbers are different, this can be related to the "Pre-Release" (book) that system crates Journal Transaction first with the pre-book then again with the release action.  You can check it by looking in the Journal Transaction > references.  ... View more

Hello Daan,    there is a default report available in the Financials ERP which is called "Aged period" (ScreenId=AR630500) would it be corresponding with what you're looking for ?    Please review that if it'd serve the purpose, then we can check for implementation options for the API. Thanks !  ... View more

Hello Mahmoud, I assume this is a POST operation where the JSON has been created based on the fields selected in the excel file.  This error might be related to the JT number used in consecutive requests, so do you know what is the interval between POST requests ?    ... View more

Hello Quan,    since you're sending "Branch" Value, could you check the payment method settings and allowed cash accounts under that based on branches ?        ... View more

Hello, do you know if the manual numbering activated for the Customers in that company ?  Could you possibly try adding  "number": { "value": "xxxxx" },   ... View more

Alright, thanks for the confirmation then !  ... View more

No problem ! Please let us know if you need any further clarification  ... View more

Hello, we confirm the issue. We're unable to PUT "expirationDate" field via Shipment Endpoint when LOT is Expiration Date Tracked. 1) PUT Shipment with Allocations - ExpirationDate   "shipmentDetailLines": [ { "operation": "Update", "lineNumber": { "value": 1 }, "allocations": [ { "operation": "Update", "lineNbr": { "value": 2 }, "location": { "value": "2" }, "lotSerialNumber": { "value": "000010" }, "UOM": { "value": "STK" }, "quantity": { "value": 1 }, "expirationDate": { "value": "2023-03-23T00:00:00" } } ] } ] }   2) HTTP Status: 204 3) "ExpirationDate" field/s are not updated.   This has been reported to the development team. Thank you for bringing this to our attention.  ... View more

Could you please send the ipp-company-id via developersupport@visma.com ?  ... View more

Hello, the root cause has been identified. When using the service-api, a system-generated user will be created (first time) on-the-fly, for the client. There might be some endpoints that require the user to be an employee. For service-api, the user is not an employee.   Currently, the development team is looking into that. We'll keep you informed of any progress. ... View more