to get a personalized navigation.
to get a personalized navigation.
We are getting the error tstamp cannot be empty when trying to update a supplier invoice using the endpoint: "/controller/api/v1/supplierInvoice/{documentType}/{invoiceNumber}". This is replicateable for the customers environment (tenant id: 91a72b61-baa7-11ea-973a-0ac295605980) and the JSON body:
{"SupplierNumber":{"Value":"51169"},"SupplierReference":{"Value":"61712917"},"Note":{"Value":"https://cloud.mediusflow.com/******/#/Tasks/ShowDocument/108364"},"CurrencyId":{"Value":"NOK"},"DueDate":{"Value":"2024-10-27T02:00:00+02:00"},"Date":{"Value":"2024-09-17T02:00:00+02:00"},"SupplierTaxZone":{"Value":"10"},"PaymentRefNo":{"Value":"617129176"},"CashDiscountDate":{"Value":"2024-10-27T02:00:00+02:00"},"InvoiceLines":[{"LineNumber":{"Value":1},"Operation":"Delete"},{"LineNumber":{"Value":2},"Operation":"Delete"}],"DocumentType":{"Value":"Invoice"},"addPOReceiptLines":[{"poReceiptNumber":{"Value":"016162"},"poReceiptLineNumber":{"Value":1}}]}
This error has been repeatedly occuring since tuesday. Any ideas or suggestions? This seems to only occur when we have the field addPOReceiptLines is containing a value.
Hi Erik! Thx for your post, I have analysed this and was able to reproduce the scenario. I have reported this internally and will come back to you when I have more information.
Our development team has pinpointed the issue causing this particular behavior. A solution is now being tested, and findings look promising. We'll keep you posted as we progress. Thank you for your patience and understanding.
Copyright © 2022 Visma.com. All rights reserved.