Update to latest version of Moneydance

David Lombard's Avatar

David Lombard

20 Jun, 2019 04:01 PM

Hi,

I have just updated to the latest version of Moneydance. The process seemed to go ok but then I noticed a new account is showing on the summary screen called Restoredb3d1cde8-5ce2-4069-bce3-b9b4031e7b2a. It contains £128,600.00. What is this, where has it come from and how can I get rid of it

Showing page 2 out of 2. View the first page

  1. 31 Posted by alex.f on 27 Jul, 2019 02:07 PM

    alex.f's Avatar

    Thank you David!

    I saw that 1886 was out there and I downloaded it, but since I had not seen any mention of it I thought I would hold off until it was formally announced. I had thought about suggesting 1886 to you in my earlier reply but I didn't want to suggest something that I had not tried myself. Since it is working for you I might give it a try.

  2. 32 Posted by David Lombard on 27 Jul, 2019 02:27 PM

    David Lombard's Avatar

    Hi Alex,

    I am using Version 2019.3 (1881)

    Regards,

    David

    ________________________________

  3. 33 Posted by cdr on 27 Jul, 2019 11:53 PM

    cdr's Avatar

    Does anyone know if the latest beta version 1886 fixed the phantom "restored" account problem?

  4. 34 Posted by david on 28 Jul, 2019 03:14 AM

    david's Avatar

    Yes - Build 1886 solved the unwanted account problem on my system

    — —David G.

  5. 35 Posted by yardy on 28 Jul, 2019 12:25 PM

    yardy's Avatar

    I had restored to 2019.1 from 2019.3 to get rid of the Restored Account problem. So today tried 2019.4 which is claimed to solve the Restored Account issue. I got the same Restored Account problem, so as far as I am concerned, this issue is NOT solved.

  6. 36 Posted by cdr on 28 Jul, 2019 08:35 PM

    cdr's Avatar

    I decided to give the latest beta (1886) a try.
    After I backed up the previous version, just in case, I installed the new file.
    So far all is well and no sign of the phantom restored file.
    I will post if any issues arise.

  7. 37 Posted by alex.f on 29 Jul, 2019 01:55 PM

    alex.f's Avatar

    I just tested build 1886 and I once again see a "Restored" account.

    If I open the console, I see this error which looks to be related:

    couldn't find account based on legacy ID (1449062) or uuid (3028d10c-32e2-46e4-9cd7-961dd322a236). Using fallback account for now. From txn:20110722 Employee Contribution Transfer 15401 c4e7a34f-f729-45b4-96e1-a008dbd9513b

    The Restored account has the UUID beginning 3028d as part of its name.

    I was hoping this was going to be resolved, but apparently it needs more attention.
    Unfortunately, I am going to revert back to 1855 again.

  8. 38 Posted by alex.f on 29 Jul, 2019 02:15 PM

    alex.f's Avatar

    Reverted to 1855. The restored account is gone, but I do see the following errors in the console which have probably existed for a while:

    couldn't find account based on legacy ID (1449062) or uuid (3028d10c-32e2-46e4-9cd7-961dd322a236). Using root account as fallback for now. 20110722 Employee Contribution Transfer 15401
    couldn't find account based on legacy ID (1449062) or uuid (3028d10c-32e2-46e4-9cd7-961dd322a236). Using root account as fallback for now. 20110617 Employee Contribution Transfer 15401
    couldn't find account based on legacy ID (1449062) or uuid (3028d10c-32e2-46e4-9cd7-961dd322a236). Using root account as fallback for now. 20111230 Employee Contribution Transfer 15401
    couldn't find account based on legacy ID (1449062) or uuid (3028d10c-32e2-46e4-9cd7-961dd322a236). Using root account as fallback for now. 20111028 Employer Match Contribution 7700
    couldn't find account based on legacy ID (1449062) or uuid (3028d10c-32e2-46e4-9cd7-961dd322a236). Using root account as fallback for now. 20071026 Employer Match Contribution 4904
    couldn't find account based on legacy ID (1449062) or uuid (3028d10c-32e2-46e4-9cd7-961dd322a236). Using root account as fallback for now. 20120127 Employee Contribution Transfer 15401
    ...

    There are another 45+ lines like these but I don't see the need to paste them all. They do correspond to what shows up in the Restored account I see with recent builds. I believe these transactions are related to my attempts to track my 401k deductions from my paycheck deposits and match them to my 401k account which I was also tracking (at the time in Quicken.) Since I changed jobs since then, that 401k account no longer exists in my set of accounts. What is interesting is that these transactions are a small subset of the number of similar transactions.

    I am wondering if I should just upgrade and then add an offsetting transaction to bring the Restored account balance to zero and then hide it? Not ideal but I would like to update to a more recent release.

  9. Support Staff 39 Posted by Sean Reilly on 08 Aug, 2019 11:18 AM

    Sean Reilly's Avatar

    Hi Alex,
    Yes, the entire "Restored account" thing is really just surfacing an inconsistency in the data that may have been there all along and just not visible. Would you be able to run the latest preview version and then, if the Restored account" still appears, check to see if there are any non-zero transactions in it, and if so, delete them. To be safe I would make sure that no scheduled transaction reminders contain a reference to the restored account. Once that is done, you should be able to deleted the restored account and have it never re-appear.

    Thanks!
    Sean

    --
    Sean Reilly
    Developer, The Infinite Kind
    https://infinitekind.com

  10. 40 Posted by alex.f on 08 Aug, 2019 12:50 PM

    alex.f's Avatar

    Thanks Sean!
    I installed build 1888.

    Here is the current problem: If I try to delete a transaction from the Restored account it impacts the balance on my current checking account since these transactions are tied back to that account.

    Is there a good way to recategorize them so they are still tied to the checking but not tied to the Restored account?

  11. Support Staff 41 Posted by Sean Reilly on 09 Aug, 2019 07:44 PM

    Sean Reilly's Avatar

    Hi Alex,

    Yes, you should be able to recategorise them by right-clicking (or ctrl-clicking) on the transaction in the Recovered Account register and selecting "Show Other Side" which will take you to the other account and begin editing the transaction from that side, changing the category for the account from the "recovered" account to a normal category.

    Thanks,
    Sean

    --
    Sean Reilly
    Developer, The Infinite Kind
    https://infinitekind.com

  12. 42 Posted by alex.f on 09 Aug, 2019 09:40 PM

    alex.f's Avatar

    Thank you Sean!

    That indeed worked, although it was a bit of a tedious task. I created a new category and changed them all from the Recovered account to the new category.

    So the Recovered account is now gone. I am no longer seeing any errors in the console. Build 1888 looks good so far.

    Thanks again,
    Alex

  13. Support Staff 43 Posted by Maddy on 10 Aug, 2019 10:31 AM

    Maddy's Avatar

    We are very pleased to hear that, Alex.
    I'll close this discussion for now, but do not hesitate to contact us again, if you need further assistance.

    --
    Maddy, Infinite Kind Support

  14. Maddy closed this discussion on 10 Aug, 2019 10:31 AM.

  15. rayplayer re-opened this discussion on 11 Aug, 2019 06:24 PM

  16. 44 Posted by rayplayer on 11 Aug, 2019 06:24 PM

    rayplayer's Avatar

    Unfortunately, this workaround does not work for me - I upgraded from 2019.1 (1855) to 2019.4 (1888) and a 'new' account Restored cd53dbce-1e39-4791-8baa-93e85d0390c3 appeared.

    I created a new category '2019.4 1888 'New' Account Workaround' and have successfully recategorized two entries by selecting "Show Other Side" which took me to the other account so that I could edit the transaction from that side, changing the category for the account from the "recovered" account to my new category. Unfortunately, there are two remaining entries that can not be edited.

    When I edit and am asked 'Save Changes to Transaction' as is normal but despite saying Yes, when I select the 'new' account to navigate to it I am asked again 'Save Changes to Transaction'. Saying Yes gets me to the 'new' account where its apparent no change has been made. I have repeated this several times.

    BTW I went to 'Edit Account' to copy the name for this comment and it has resulted in another 'new' account being created with the same name! I now have two 'new' accounts - strangely one of the two transactions moved to the other new account (nothing I did).

    Clearly, all of my balances are incorrect now, hence have now reverted to 1855 where everything is working as it should.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:

»

Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts

Generic

? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac