Describe the bug
Transactions cannot be edited to change the source account. In the transaction list, clicking on one to access the edit form, changing the source account (to an already existing one) and pressing Submit, the popup shows Sucess but the transaction remain unchanged.
I checked the Firefly logs following the app request, and then did the same transaction edit from the Web UI to compare the logs. I can make them available but they are quite marge and full of personal info. And the HTTP requests content is not logged in the server logs.
Though comparing the logs it seems that from the Web UI, selecting an existing account in the form will then set the account ID in the request, while in the request from the app there is only the account name, even if the account is selected with the autocomplete in the form:
The source_id and destination_id are then propagated as null, which might be the root cause, see around line 96/98.
Then the source account is not valid:
To Reproduce
Steps to reproduce the behavior:
Go to Transactions
Click on any transaction to open the edit form
Change the source account to an already existing one
Click Submit
The request is successfull, but the transaction's source account is unchanged
Expected behavior
The transaction should be updated as per the form's values.
Smartphone (please complete the following information):
Device: iPhone
OS: 16.7
Version: 0.15.0
Additional context
None, thank you very much for this amazing app!
Describe the bug Transactions cannot be edited to change the source account. In the transaction list, clicking on one to access the edit form, changing the source account (to an already existing one) and pressing Submit, the popup shows Sucess but the transaction remain unchanged.
I checked the Firefly logs following the app request, and then did the same transaction edit from the Web UI to compare the logs. I can make them available but they are quite marge and full of personal info. And the HTTP requests content is not logged in the server logs.
Though comparing the logs it seems that from the Web UI, selecting an existing account in the form will then set the account ID in the request, while in the request from the app there is only the account name, even if the account is selected with the autocomplete in the form:![image](https://github.com/victorbalssa/abacus/assets/12754559/a335479a-0721-495f-8b58-e5f6999c371b)
The source_id and destination_id are then propagated as null, which might be the root cause, see around line 96/98. Then the source account is not valid:![image](https://github.com/victorbalssa/abacus/assets/12754559/2a65909f-6ed0-432b-92ad-4c1789cc87d8)
To Reproduce Steps to reproduce the behavior:
Expected behavior The transaction should be updated as per the form's values.
Smartphone (please complete the following information):
Additional context None, thank you very much for this amazing app!