Nasty "new transaction line" bug in register
I'm a new user to Quicken so I was just playing around getting a feel for the software. I created an AR account to test out how invoices work and noticed some funny behavior when I was trying to delete the invoices I created and ended up finding a bug in the software. It seems like the first invoice created, even though it looks like a legitimate invoice, cannot be modified, and if you do modify it, it will create another invoice. Here's a video describing the behavior:
youtu.be/tn9-l9m_KKg
I created a video and linked it to this post. I also have a ticket number that you can reference if you're running into the same issue:
11224765
After I typed all of the above and played with this some more, I think I figured out what's going on - it looks like the issue stems around the sort order and where the empty "new transaction" line ends up. What it looks like Quicken is doing (in my example, which is completely default) is assuming that the bottom transaction is that special "new transaction" line, even though it's actually at the top. If you then modify that bottom transaction, it adds a new transaction - what's weird is that if you use the real "new transaction" line that's at the top, it will also add a new line.
If you change the sort order such that the "new transaction" line is at the bottom of all of your transactions, then it seems to behave normally and you can modify/delete whatever you want (what I was initially trying to do). I tried multiple account registers and they all seemed to be affected by this. Just by changing the sort order, that'll get things working correctly - in other words, make sure the "new transaction" line is always at the bottom!
They said that this would be fixed in the next version, but I'm not sure when that is… I submitted this 8/13/2024 so hopefully it's fixed soon because this is not good when transactions can't be modified and/or mysteriously spawn new transactions that end up affecting your register balance!
Comments
-
Just FYI, I checked my friend's Quicken version from 2 years ago and it also has the same issue, so this bug has been around for years. Make sure you sort your registers by date with the newest transactions at the bottom to avoid running into this issue.
0