Changing the date of a transaction from the mobile app removes the tags
Hi,
Here are the steps to reproduce this problem.
1. Enter a split transaction in any bank/cash account with a memo and tags for each split, and let it sync to the mobile app.
2. Open the mobile app and change the date of the transaction.
3. Check the same transaction in the primary application on your laptop with the updated date in the account after a sync.
Results = the tags would have all been removed.
App Versions: Moneydance 2024.3 on Windows 10. Latest Version of Moneydance on iOS 18.
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 dtd on 13 Feb, 2025 02:52 AM
Although you mention this as being a problem on Moneydance 2024.3, this is not a new issue, as I don't think tags are passed to the mobile device, so if you edit a transaction as you describe above, the mobile device does not have the tags, so passes back the same transaction with a changed date and no tags.
I just verified this is an issue in 2024.2, so you are reporting an issue that I think is a known one.
Someone else may correct me if I'm wrong, as I almost never use tags.
2 Posted by Stuart Beesley ... on 13 Feb, 2025 06:16 AM
I don’t know if it’s ‘known’, but it is now. Thanks for reporting. Certainly an annoying one that needs fixing. I presume you get the same issue if you edit any field?
3 Posted by Stuart Beesley ... on 13 Feb, 2025 10:38 AM
I’ve reproduced this issue too…
4 Posted by Stuart Beesley ... on 13 Feb, 2025 11:58 AM
The issue has been identified. I would anticipate the fix for the first alpha of the 2025.x series…. (Just a guess on that last point)
5 Posted by Ali on 13 Feb, 2025 11:11 PM
Thanks dtd - I just think if it’s a known issue then ideally should be documented as such in the help guides so that users are warned not to modify any transaction with tags in the mobile app.
Thanks Stuart - love the responsiveness!
6 Posted by dtd on 15 Feb, 2025 02:01 AM
Ali - I agree with you. I would love to see a list of known bugs be available, but MD doesn't list such.
As Stuart says, by posting, you made other users (me, Stuart, etc) aware of the bug. My response was mostly due to we users are currently watching for bugs that might appear in 5219 that were not there before, and I noted that this bug (and it's not minor!) existed before this release.
We take the bugs we find (currently looking for 5219 bugs - happily there are very few unique to 5219) and reporting them 'up the line'. As I noted, this is an older bug, but we users agree it's one to look at trying to get prioritized.
7 Posted by Stuart Beesley ... on 15 Feb, 2025 06:07 AM
It’s now been fixed ready for 2025.x
8 Posted by Stuart Beesley ... on 16 Feb, 2025 06:39 PM
In fact this is now fixed in post 2024.3(5252) alpha, which is just 2024.3 with 3 small fixes in (including this one in it).. Up to you if you want to test this fix. As always, health warning, and BACKUP first!
9 Posted by Stuart Beesley ... on 20 Feb, 2025 04:57 AM
Sorry to report this still appears broken in 5253 (even with the 'fix')
10 Posted by Stuart Beesley ... on 20 Feb, 2025 02:30 PM
OK, after further discussion with the developer.... The code to fix this is there, but not really enabled yet. Basically, this cannot be turned on until MD2025 when enough time has passed that all data that needs to sync can use the "new" internal UUID reference numbers (rather than the old integer 'dumb' numbers)... So, I expect this will be enabled for the first 2025 alpha and then people will start testing this doesn't break sync...
11 Posted by Ali on 20 Feb, 2025 05:29 PM
Thank you for these ongoing updates! It's not a deal-breaker for me personally given I only use the iOS app to enter transactions and tag them later in the main app.