#34 Net worth graph changes with account name change

[Anonymous]

I've noticed that if you change the name of an account, it screws up the graphs for net worth. I recently changed the name of one of my savings accounts from ING savings to Travel fund. When I did, I noticed that both of the net worth reports became incorrect. The reports for "today" are always correct, but for any day previous it shows a lot less money in the account than there actually was, resulting in a giant spike in the net worth reports.

For example, in the "breakdown of net worth as of" report, if I choose today, it shows correctly (with the account having a little over $6000). However, if I choose yesterday, it shows the same account having just over $1500, even though no activity has occured (other than changing the account name). This also creates a big spike in the "breakdown of net worth over the past" report.

I've attached a couple of pics of the program windows for reference, showing todays net worth and yesterdays (both reports show the account name as ING savings. I changed the account name back, hoping it would fix the problem, but it didn't)

[Nobody/Anonymous]

Picture of the bug in the reports

[Wyatt]

Logged In: YES
user_id=1200533
Originator: NO

To revert to an older data file, you can load a backup file Data.X.buddi, located in the same directory as the data file. Click on File -> Restore Data File from Backup.

I will also take a look at this, and see if I can reproduce it on my system.

Thanks for the report.

[Wyatt]

Logged In: YES
user_id=1200533
Originator: NO

This is now corrected. The problem was that when I updated the account, I also (mistakenly) reset the creation date. In the reports (when a report is based on date), I check the creation date and don't include any transactions before that date - thus, that account was not included in the net worth graphs until the present day (which is why the amount finishes up in the correct location).

To fix your problem, you will have to restore to your backup file from before the rename. After you download the fixed version, you can then rename the account as desired.

This bug is fixed in 2.0.5 / 2.1.9.

Cheers
--Wyatt