You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When I have expense account set to 'not active' and then create a withdrawal and fill in the name of the expense account (or, I get a suggestion after typing the first few letters and select it), I end up with two expense accounts with the same name. One active, one inactive.
I would expect the inactive account to become active again, and the withdrawal going into that account. I have tested this on the demo site and the same thing happens there, however, I did set the expense account to inactive manually. On my server I've had this experience with automatic inactive accounts.
Related to this: what is the idea behind setting accounts to inactive automatically? For speed?
Would it make more sense to activate the original account when I create a new transaction with that expense account name?
The text was updated successfully, but these errors were encountered:
I didn't edit accounts directly as far as I remember, but I did merge a couple and moved transactions from one expense account to another. I had imported a bunch of transactions (thousands... dating back to 2006 😉 ) and needed to do some cleanup, I didn't check after every change I made...
It hasn't happened since the latest update and I'm still doing cleanup so I think that whatever caused it got fixed, but I'll keep an eye on it, just in case.
When I have expense account set to 'not active' and then create a withdrawal and fill in the name of the expense account (or, I get a suggestion after typing the first few letters and select it), I end up with two expense accounts with the same name. One active, one inactive.
I would expect the inactive account to become active again, and the withdrawal going into that account. I have tested this on the demo site and the same thing happens there, however, I did set the expense account to inactive manually. On my server I've had this experience with automatic inactive accounts.
Related to this: what is the idea behind setting accounts to inactive automatically? For speed?
Would it make more sense to activate the original account when I create a new transaction with that expense account name?
The text was updated successfully, but these errors were encountered: