MD update makes $ amounts nonsensical
Upgrading from 2022.5 (4091) to 2022.6 (4097) gave me quite a scare. On the initial run of the new instance multiple accounts without apparent reason showed values dramatically different from their previous values. These changed dynamically as I selected different accounts in the left pane. Some transactions previoulsy recorded in the register showed different categories than those that were initially assigned. Disconcerting to say the least!
Reverting to the previous version restored the expected values, so nothing appears to have been changed in the database.
Running 4097 again, things look normal, so it looks like a transient, but I thought I should report it regardless.
Perhaps related, I initiated iCloud synching shortly before performing the upgrade.
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
1 Posted by Stuart Beesley ... on 01 Feb, 2023 10:24 PM
There is almost no difference between 4091 and 4097. There were a couple of sync tweaks. Syncing can cause balances to change whilst syncing.
Can you upload help/console whilst running 4097
Also, I suggest you use toolbox, advanced, force refresh/push sync data to rebuild sync.
2 Posted by Glen on 01 Feb, 2023 10:46 PM
Did the Force sync, still no file system objec visible in the iCloudfolder.
Attached console output.
3 Posted by Stuart Beesley ... on 02 Feb, 2023 07:22 AM
No errors
To clarify, you are still saying all is ok on 4091 and not on 4097?
Also is this on a primary or sync’d copy of moneydance?
If on a secondary, is the primary ok?
4 Posted by Glen on 02 Feb, 2023 02:28 PM
I am working with the primary syncher.
Both versions now show identical data. I think I was just misunderstanding what was going on. But flashing up a dialog box with "Sync in progress" seems less likely to cause concern than having account values changing before one's eyes.
The unexpected transaction issue mentioned in a previous post is unrelated.