Hello,   One of our customers works with independent contractors. A contractor can change the country where they work, and in that case different VAT rules apply.    Our customer uses several Supplier classes for the different VAT situations and through the API wants to set the supplierClassId of the suppliers/creditors accordingly.   We have now encountered a situation where the update of the supplierClassId fails regularly.    We've tested this with:   { "supplierClassId": { "value": "ZZPNL" }, "overrideWithClassValues": true }   And the response is:   { "message": "VismaId: 3f3af37e-ee71-4b27-bca8-bd2a719b40ce. Error updating the supplier. Error: Another process has deleted 'Address'. Your changes will be lost." }   Can you please give us an idea of what could be the reason for this message?   Thanks! ... View more

Hello,   We ran into the following situation: a customer/debtor has earlier been given a Parent Account either through the UI or through an API call.   At some point we'd like to empty the parent account field of this customer record by setting a null value, using:  PUT /controller/api/v1/customer/{customerCd}   and:   [CODE] { "parentRecordNumber": { "value": null } } [/CODE]   This will fail, and the following error is received: [CODE] { "message": "By activating this setting, invoices created from orders will be sent to the parent customer. Invoice related settings will be collected from the parent customer. See the help for details. Do you want to activate this setting?" } [/CODE]   Result: the Parent Account value is not removed.   After some trial and error we noticed that when we first manually remove the Parent Account through the UI, then afterwards all PUT calls succeed.  So then we can: - set a new value through API - use null to empty the value   - set a value manually - use null to empty the value   The above behaviour we see both in our client's company as well as in a test company of our own.   Thank you for you advice in this. ... View more

Hello,   One of our customers reports that a GET on the CustomerPayment endpoint no longer returns the correct value for field 'balanceWriteOff' in the paymentLines. It now always return the value zero.   In the user interface however it shows a value (e.g. 6). It is a field called 'Balance write-off' (datafield DisplayCuryWOAmt) on the tab 'Application history'.    They periodically do a GET to update data in their CRM system. They notice that also older payments, for which in the past the correct value was returned, now have a value 0.   Up until recently this worked fine. Has there been a recent change on this part in the API?   Thank you for your reply! ... View more