Force delete account?

[tralph3]

I imported a csv file on a test account to see if it would work. It did, but now I don't want this account, however, because there's transactions associated with it, I can't delete it as it complains its in use. Can all the associated transactions be deleted with it?

[mayswind]

this feature is not supported now, but it can be added

[tralph3]

I tried modifying the database to do this manually myself, and while it did appear to work, the account balance was off as its also stored in the db, but then there were transfer transactions from other accounts that shouldn't have been deleted.

A force delete would very much be appreciated.

[tralph3]

It would also be cool to have that feature you have when importing about batch modifying transactions. If in the transaction list we could select specific transactions (with filters applied and such) then we could apply the same transformations.

This would make it trivial to delete all transactions in the account, without a real need for a force delete. I could filter the transactions to only include the ones for that account, select them all, then delete them all.

Also, the error message could probably be improved. "Can't delete because it's in use" is not really that clear. "Can't delete because it has transactions" could be better, but if there's other reasons (like the account being set as default, or having templates that include it) then maybe the error message could change depending on the situation to make it easy for the user to resolve it.

[mayswind]

1. When importing transactions in ezBookkeeping, you can batch modify them. You can click the three dots in the top right to try it out
2. In ezBookkeeping, accounts, transaction categories, and transaction tags can’t be deleted for just one reason—they’re being used by other transactions. The error message already makes this clear, so I don’t think it needs to be changed

[tralph3]

When importing transactions in ezBookkeeping, you can batch modify them

Yes, exactly. I'm proposing extending this functionality into the regular transaction list. That way mass deleting would be easy.

[mayswind]

ezBookkeeping would not support batch modifying transactions, because this can easily lead to mistakes and irreversible data loss.
Batch modifying is only available when importing transactions, since all data during the import process is temporary. So, users can make large-scale changes without permanent consequences. Moreover, batch modifying is genuinely useful in the import workflow, whereas for most users, it isn’t necessary once transactions have already been created.