Setting or changing the property ‘enshrined’
- One minute read - 159 wordsEnshrined objects should not be modifiable.
Status Quo:
In sevDesk system version 1.0 it is possible to directly set and unset / change the value of the property enshrined for Invoice, Voucher, CreditNote and CheckAccountTransaction. This is already not possible in sevDesk-Update 2.0.
Future:
The property enshrined must be set via the dedicated endpoint. It can no longer be set directly.
- PUT /api/v1/Invoice/{invoiceId}/enshrine
- PUT /api/v1/CreditNote/{creditNoteId}/enshrine
- PUT /api/v1/Voucher/{voucherId}/enshrine
- PUT /api/v1/CheckAccountTransaction/{checkAccountTransactionId}/enshrine
Once the property enshrined was set it can no longer be unset or changed. Attempts to do so will result in a HTTP-Status code 422.
This now also applies to sevDesk-Update 1.0, so that the behaviour of 1.0 and 2.0 will be unified.
Affected endpoints:
- POST /api/v1/Invoice/Factory/saveInvoice
- POST /api/v1/CreditNote/Factory/saveCreditNote
- POST /api/v1/Voucher/Factory/saveVoucher
- POST /api/v1/CheckAccountTransaction
- PUT /api/v1/CheckAccountTransaction/{checkAccountTransactionId}
Does also affect these unofficial endpoints (these should not be used anyway, as they will be removed in the future):
- POST/PUT /api/v1/Invoice
- POST/PUT /api/v1/Invoice/{invoiceId}
- POST/PUT /api/v1/CreditNote
- POST/PUT /api/v1/CreditNote/{creditNoteId}
- POST/PUT /api/v1/Voucher
- POST/PUT /api/v1/Voucher/{voucherId}
Release: 23.07.2024 (4.184)