Same issue with lineDescription on salesoderV2. The description is not being posted from the code.    ... View more

SalesOrderV2 endpoint   ... View more

Dette er en funksjon som er veldig etterspurt fra flere av våre kunder, håper denne blir prioritert utført snart.    mvh Steinar ... View more

I did the same test now and it seems to be working as it should and using the correct sales account. I am not able to reproduce the same error,  so I believe that this case is not relevant anymore. Maybe Florian still has the same problem?   ... View more

Hi, Is there any change that this field will be exposed in the CustomerInvoice POST in the near future?  ... View more

Hi, Yes the original issue is solved. 1. Shipping address issue is solved and now working. 2. This is still an issue, when ShipVia is posted along with CustomerVATZone.   ... View more

Hi Yildirim, I have already attached print screen from UI in the above post.       ... View more

Hei, Henger meg på innspillet fra @Kari van Riessen, en hurtigtast til Autopay er savnet og ønskelig.      ... View more

Hi, This is still not working and we have done a lot of testing with the json posted, I have removed one by one field from the code for finding what is affecting why CustomerVATZone are not posted.  When we post with the shipVia field CustomerVATZone are not posted, without the shipVia, the customerVATZone are posted. Ex: }, "shipVia": { "value": "UPS STANDARD" }, Please test this and confirm if this is a bug.   ... View more

Hi, We still haven't get any update on this issue. The customer must still manually adjust all the salesorder when they are posted.  Can you please give me an update on this?   brgds Steinar ... View more

Hi Magnus, Any update of this issue? We got the same problem on another customer today. Same code running and gives no string and empty body back from the Inventory endpoint.  Will you please update us on this?  ... View more

Hi, What is status on this issue? We still have the problem and need this to be solved. ... View more

I have now done some new testing and getting same issue. Posting to a customer set to customer class=2  "International customers free of charge". When posting with V2 endpoint gives the wrong account (sales account taxable, set from the item), posting with V1 it gives the correct account (sales account non taxable, set from the item). This is working as it should posting manually. It seems that there are different handling in V1 and V2 and that V1 gives the correct posting.   ... View more

Do you have the json from your test where this is working? Attached json from this customer.  ... View more

Hi, I testet with V1/customerInvoice, and there the accountNumber was posted correctly. It seems like the problem occurs in V2. ... View more

Attached details. ... View more

Hi, We having exact the same issue from one of our customers. They are posting invoices without any accountNumber in the json, and the customerInvoice is posted with wrong account. When posting manually in UI with same customer and items, the correct account is posted.  This occurs on invoices posted with foreign customer, the customer are configured to use "sales non-taxable account" but when posting from API, the account used is "sales account".    Do you have any solution for this issue?   brgds Steinar ... View more

Hi. Good neews. We have got no errors related to this so far today. We will continue monitoring.    Brgds Steinar   ... View more

Hi, We have the same issue and it's really critical. We see this in several endpoints, Inventory, SalesPrice, Customer, SalesOrder etc. Hope this will be solved as soon as possible. Thanks. Log from system errors since last   03:59 31.08 5102 03:20 31.08 5102 og timeout 23:18 30.08 5102 22:41 30.08 5102 22:23 30.08 5102 21:06 30.08 5102 20:38 30.08 5102 19:47 30.08 5102 19:30 30.08 5102 16:20 30.08 5520 og {"message":"VismaId: 97fe0349-e41f-411e-a5fd-b01c1abeaf54. A network-related or instance-specific error occurred while establishing a connection to SQL Server. The server was not found or was not accessible. Verify that the instance name is correct and that SQL Server is configured to allow remote connections. (provider: Named Pipes Provider, error: 40 - Could not open a connection to SQL Server)"} og 502 bad gateway. We also have the issue with not getting any response when we are posting, missing 201 request. Reported earlier. this has now been a problem for 2-3 weeks.    Ex errors: /controller/api/v1/Inventory?attributes=%7B%22BUTIKK3%22%3A1%7D&availabilityLastModifiedDateTimeCondition=%3E&availabilityLastModifiedDateTime=2021-08-31 01:49:46&pageNumber=1 {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_a9279539-a9be-4059-856c-c191c838d45c","ExceptionDetails":""} /controller/api/v1/customer?status=Active&corporateId=986503781&pageNumber=1 {"ExceptionType":"IPPException","ExceptionMessage":"","ExceptionFaultCode":"5102","ExceptionMessageID":"5102_69533f9a-384c-4351-b8a8-4caae57365df","ExceptionDetails":""}   ... View more