We're aware that the thread has been marked resolved by misstake, we're still investigating. ... Meer weergeven

I've sent a few examples to developersupport now ... Meer weergeven

Hi, We'll forward this to the development team. Thank you.  ... Meer weergeven

Hi, This error code is generally due to a network issue, have you retried the operation since? Thank you.  ... Meer weergeven

Hi, As of today, the cutomerPayment endpoint does not have any lineNumber property in the invoiceLines array. If this is something you need, please create a post in the "Ideas" part of the forum. ... Meer weergeven

Hi Stefan, Ok, thank you! ... Meer weergeven

Hello Magnus, Could you again check the status of these ideas? Greets, Michel ... Meer weergeven

For the breaking changes we will follow the same guideline as what is today in the Visma.net ERP API, i.e. latest 3 months before. In the closest roadmap we have not planned to introduce createShipment in V3. Could you elaborate a bit more for why it is highly needed in V3? Is it, for example, for the easier use of the API through the sales process or expectation of better performance in that endpoint etc? ... Meer weergeven

Hi, I'm getting the same error with this body and i can't see anything wrong with the customer number sequence. It is possible to create the payment in the UI.    "message": "VismaId: 7e72a23f-5cb7-4853-895c-51c08010bc2b. Error creating payment Error: Inserting  'Customer payment' record raised at least one error. Please review the errors.\r\nLast reference number customers\r\n"   {     "branch": {         "Value": "1"     },     "currency": {         "Value": "SEK"     },     "customer": {         "Value": "10089"     },     "type": {         "Value": "Payment"     },     "paymentRef": {         "Value": "Reglering"     },     "cashAccount": {         "Value": "1973"     },     "paymentMethod": {         "Value": "03"     },     "applicationDate": {         "Value": "2023-10-13T00:00:00.000Z"     },     "paymentAmount": {         "Value": 87603.75     },     "paymentLines": [{             "refNbr": {                 "Value": "1902396"             },             "documentType": {                 "Value": "Invoice"             },             "amountPaid": {                 "Value": 87603.75             },             "crossRate": {                 "Value": 1.000000             },             "operation": "Insert"         }     ] } ... Meer weergeven

last 10 days commer vatId without any problems. We'll have to wait and see how things turn out in the future. ... Meer weergeven

Hi Actually it seams to have been solved now. Its working.   /Anders ... Meer weergeven

This is of great need, so please extend the response with this as soon as possible. ... Meer weergeven

Hi, We've been unable to recreate this issue so far. Could you please send us an email with the companyID, details regarding how this was set up? The development team will have to take a look at the company database. Thank you.  ... Meer weergeven

Thanks... I missed that one ... Meer weergeven

But this does not return the Items page ( locations) either. ... Meer weergeven

Hi, That depends on how your customers have their subaccounts set up. ... Meer weergeven

Hi, If you are sending the below fields in each call, you are choosing to overwrite the values with the default value in the class. Does the customerClass "EUSTD" have paymentMethod 1 set? "OverrideWithClassValues": true, "CustomerClassId": { "Value": "EUSTD" } ... Meer weergeven

If you still have problems initiate a chat on ms teams and I can try to help out thomas dot adrian @ consili.se ... Meer weergeven

Hi,    That seems to be exactly whats happening, that also explains why some orders works and some dont.  Thank you. ... Meer weergeven

Ok, but please implement it very soon as we are in great need of it. ... Meer weergeven

Alright, if you have a list of the calls, preferably with the request id, and send it together with the clientID to developersupport@visma.com we'll have a look at it and pass it on to the development team.  Thank you.  ... Meer weergeven

Hi, Thank you.   Yes, I have tried that. I get a 204 response but the transfer number field is not updated/populated on the inventory receipt, so no luck there either.   Example: PUT: https://integration.visma.net/API/controller/api/v1/inventoryReceipt/2700193 Headers: { Accept: application/json Authorization: <hidden> Accept-Encoding: gzip Accept-Encoding: deflate Request-Id: |mNxxPaa2S54=.73b6c807_5. Content-Type: application/json; charset=utf-8 Content-Length: 38 } {"transferNumber":{"value":"2700188"}} Response: 204 No Content Headers: { Date: Fri, 25 Aug 2023 14:50:32 GMT Server: Nginx Strict-Transport-Security: max-age=31536000; includeSubDomains Strict-Transport-Security: max-age=31536000; includeSubDomains ipp-request-id: f8e62102-bed6-49b2-96e7-fc42bdce0789 X-Content-Type-Options: application/json Pragma: no-cache X-Handled-By: Visma-PX.Export/AuthenticationManagerModule Referrer-Policy: origin-when-cross-origin VnfInstanceId: ERP_SE_DEMO_0017 Cache-Control: no-cache X-XSS-Protection: 1;mode=block Set-Cookie: <crumbs>; path=/; secure; expires=Thu, 24-Aug-2023 14:50:31 GMT; HttpOnly Expires: -1 }   ... Meer weergeven

Hi, We've asked the team for an update, we'll inform you as soon as we have an answer. ... Meer weergeven

That would help, please send it to DeveloperSupport@visma.com. Thank you.  ... Meer weergeven