API: reconciled: false
does not have precedence
#8893
Labels
Milestone
reconciled: false
does not have precedence
#8893
Support guidelines
I've found a bug and checked that ...
Description
Dealing with changes to reconciled transactions using the API is a bit unexpected.
When editing a reconciled transaction via
PUT api/v1/transactions/1234
, as soon as the request has any "protected" field the API call will fail with an error that the transaction is reconciled. This is true even whenreconciled: false
is submitted in the request, or if the "protected" field value is not changed.Debug information
Demo Page
Expected behaviour
reconciled: false
, it should un-reconcile the transaction and then proceed any changes made in the same request. Currently, areocnciled: false
request is needed, followed by a separate request to actually update any fields.amount
, but that field is not changed compared to the stored value, the request should not fail but proceed to update any other fields if applicable.Steps to reproduce
No response
Additional info
Looking at the web page, all fields seem to be filtered out of the update request when the transaction is reconciled to not fail according to the second point above. If this is the way you intend it to be, then consider this request only for the first point above (as this is quite annoying), and I'll implement something similar like the web page in the app!
The text was updated successfully, but these errors were encountered: