Hei,   I try to update POReceipts. That means that I try to delete the existing lines and insert the updated ones. (I do this because delete endpoint is missing):   But I cant get this work:   Insert of new lines works perfectly:   {"lines":[{"operation":"Insert","inventoryId":{"value":"1150"},"transactionDescription":{"value":"Glass og metall fra Næring#Veieseddel: 306650 - dato: 30.09.2020"},"receiptQty":{"value":7.68}}],"receiptType":{"value":"PoReceipt"},"receiptNbr":{"value":"306650"},"hold":{"value":false},"date":{"value":"2020-09-30T09:14:14.117+02:00"},"createBill":{"value":false},"supplierRef":{"value":"bh"}}     The same json just with the delete: {"lines":[{"operation":"Delete","lineNbr":{"value":1}},{"operation":"Insert","inventoryId":{"value":"1150"},"transactionDescription":{"value":"Glass og metall fra Næring#Veieseddel: 306650 - dato: 30.09.2020"},"receiptQty":{"value":7.68}}],"receiptType":{"value":"PoReceipt"},"receiptNbr":{"value":"306650"},"hold":{"value":false},"date":{"value":"2020-09-30T09:14:14.117+02:00"},"createBill":{"value":false},"supplierRef":{"value":"bh"}}   results in: Error updating purchase receipt. Error: Inserting 'Purchase receipt line' record raised at least one error. Please review the errors.\\r\\nError: 'Account' cannot be empty.\\r\\nError: 'Sub. ID' cannot be empty.\\r\\n\   Regards    Florian   ... View more

Hi,   we need the DELETE endpoint for POReceipt endpoint.   Regards,   Florian ... View more

Hi,   we have som trouble here. We made a api-integration for registering av serialnumber on PurchaseReceipts. The customer has not used this for a while but there was not any code changes. Now they want to use it again but it does not work any more.   Following details: CompanyId=2350700 PurchaseReceiptNo=2000182   Json: {"lines":[{"allocations":[{"operation":"Insert","lineNbr":{"value":1},"lotSerialNumber":{"value":"8105"},"quantity":{"value":1.0}}],"operation":"Update","lineNbr":{"value":1}}],"receiptType":{"value":"PoReceipt"},"receiptNbr":{"value":"2000182"}}   (originally we have here a list of 60 serial numbers, but for testing purposes we have reduced it to one - and we get the same errormessage)   Error from API:   Doing the same in UI works perfectly:   We also tried to send the location (which is chosen in UI automatically) in the Json but that did not help - we get the same error-message.   We know that this worked before, but we don't know exactly now it stopped.   This could be difficult to test for us because the customer has to send the articles. They have to register the serialnumbers in the UI just now because they can't wait for a solution here.   Any ideas?   Regards,   Florian ... View more

Hi,   we have a serious problem here:  the plan is to import PurchaseReceipts from 3. party system and place these collected by supplier and location on invoices.   Hereby the lines will contain some positiv transactions (quantity>0 and amount>0) and some negativ transactions, we thought to handle this with quantity>0 and amount<0   We have tested to place these receipts on invoices and this works nice in UI:  When it comes to the API, that won't work. Following json: {"documentType":{"value":"Invoice"},"supplierReference":{"value":"66992c3e-94bc-4d14-beb3-96236f39b2c7"},"supplierNumber":{"value":"50000"},"locationId":{"value":"LOKASJON 2"},"addPOReceiptLines":[{"poReceiptNumber":{"value":"000553"},"poReceiptLineNumber":{"value":1}},{"poReceiptNumber":{"value":"000553"},"poReceiptLineNumber":{"value":2}},{"poReceiptNumber":{"value":"000553"},"poReceiptLineNumber":{"value":3}}]}   will return following error: "{\"message\":\"Error creating supplierInvoice. The PO Receipt Line with order number 000553 and line number 1 doesn't exist in the look-up table.\"}"   thats actually a critical problem in our case - what can we do? Florian ... View more

Hi   we experience a bit problems with the location endpoint. We try to get the location details of the suppliers but this is only working for the 2 tax-suppliers which are placed in the system from the standard client-templates (supplierno 49998 and 49999). For all the suppliers we have created manually in the systems we get an empty response. its not working in any of the GET endpoints for location. Trying on customers its wokring perfectly.    Regards,   Florian     ... View more

Hi   I just got a problem which can be a bit critical for us, but I dont know how to find out of this:    We are collecting PurchaseReceipts on SupplierInvoices. To know which receipts are not processed yet we take all receipts with the status balanced and not on hold. We release the receipt first and than run a put on the supplierInvoice with  "addPOReceiptLines": [ { "poReceiptNumber": { "value": "string" }, "poReceiptLineNumber": { "value": 0 } } ],   I tested this now with 4 receipts with exactly the same content (that means I copied the same receipt 4 times). The items are non-stock. The first 3 receipts went through as expected without error.   But on the fourth I got: {"message":"Error updating supplier invoice. The PO Receipt Line with order number 000085 and line number 1 doesn't exist in the look-up table."}   So I checked in the  UI and the receipt was not placed on the invoice as the error-message says. But it was no problem to place this last receipt manually on the invoice in the UI. It was available and there was no error when I transfered it there.   I think it maybe could be some locking-problem in the database when releasing the receipts? It seems like even when the API sent the return with a success-statuscode on the receipt/release the receipt was not available for the invoice endpoint yet. I have no idea how to get around the problem. This always will result in some random error situasjons. But maybe I also take wrong about the underlaying problem here?   Florian         ... View more

Hei,   we are missing the address information on SupplierInvoice. We need this to generate EHF documents from this endpoint. In addition we are going to implement an external PDF generator based on these data.   Regards,   Florian ... View more

The note is missing on the PurchaseReceipt endpoints PurchaseREceiptDto and PuchaseReceiptUpdateDto.   We wanted to use this in an integration with a third-party system.    Regards   Florian ... View more