Unable to successfully use description option as a filter element with the Transactions Filter to generate a report
I am evaluating MoneyDance to replace quicken and move to linux, which I use for everything else. I was able easily to import a fairly large account with about 5 years of data from quicken. That went easily compared to other software I have tried, so I was very encouraged. However, reports have been difficulty for me. The most useful report for me appears to be the Transaction Filter but I must be doing something wrong because I can't get any sort of consistent result when I try to use the Description field as a filter element. All I am trying to do is filter for only transactions from a specific payee. I am using the trial version 2023.3. What might I be doing wrong? The dialog box for the Transaction Filter looks like it will fill most of my needs if I can figure it out. Thank you.
Showing page 4 out of 4. View the first page
Comments are currently closed for this discussion. You can start a new one.
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
91 Posted by Stuart Beesley ... on 28 Jan, 2024 06:20 AM
OK, good news... I have tested the updated txn filter report and the updated AND/OR logic appears to work, and also so does the Category filter..
HOWEVER, there is an issue with your data (due to qif import).... I won't bore you with the detail (needless to say it's to do with where the desc/memo data is stored on splits vs parent records), but I have passed along the data issues to the developer to see if he can improve the search further...
92 Posted by Tony Mount on 28 Jan, 2024 04:56 PM
That's wonderful news, Stuart! I can't tell you how much I appreciate your help.
I'm guessing that qif is not a very rigid standard, but I have had concerns about it and had observed some differences about it. I've also been unsure what encoding option to use when importing qif. My qif files are quite old (from Quicken 6.0 for windows). I even tried some editing of the qif file itself, but didn't seem to have much effect on things. Must be a bit of a trick to import!
Thank you again! I look forward to using the fixed code!
93 Posted by Stuart Beesley ... on 28 Jan, 2024 05:05 PM
It’s not an encoding issue. It’s about which “side” of the txn the desc/memo gets populated. In MD, when you enter a txn, the description defaults to the parent and also the first split’s description. But your import only populates one of these and the extract is looking at the other one. I’ve said that both sides’ description needs to get filtered.
94 Posted by Tony Mount on 28 Jan, 2024 05:24 PM
Brilliant! I knew there was something crazy going on! I had tried exporting transactions that I had created in MD in tab delimited format and compared them to those from the imported from my old qif. There were obvious differences, but I couldn't figure out where to go from there!
95 Posted by Stuart Beesley ... on 28 Jan, 2024 05:28 PM
A quick way to check is this.
Select an imported txn and right click. Then view txn details.
Do the same on a new/manual txn. Compare the differences.
Any key with 0.x and 1.x etc is a split line (starting at 0). The others are either normal keys, or import data. Desc and memo are the key ones to look at.
96 Posted by Tony Mount on 28 Jan, 2024 05:53 PM
Didn't know I could do that! I will check it out. Thanks
97 Posted by Tony Mount on 28 Jan, 2024 09:27 PM
Took me a little while to sort that out, but now I'm with you!
98 Posted by Tony Mount on 29 Jan, 2024 06:11 PM
Hi Stuart. How will I know when the fixed version is available? Do you expect a new version number when it is released.
Thanks, Tony
99 Posted by Stuart Beesley ... on 29 Jan, 2024 06:51 PM
Well.... I have nothing to do with IK.... but....
I'm hoping the developer will fix the latest problem I pointed out... He said he would...
I can then grab and test the code..
Hopefully will will then push an alpha or preview.. At which point, you can download to test...
100 Posted by Tony Mount on 29 Jan, 2024 06:57 PM
Thanks, keep me in the loop if you can.
101 Posted by Stuart Beesley ... on 30 Jan, 2024 01:17 PM
Good news. After numerous fixes, reworks, suggestions, reworks, retesting rounds…. The txn filter report has been fixed in the core code. My tests retrieves all the right records and totals for your desc/memo Sergio and rent category filters.
Now, as for when this will make a preview version….. ?tbc.
102 Posted by Tony Mount on 30 Jan, 2024 04:33 PM
That's great news Stuart! I shall try to wait patiently!
This should give us an easy transition out of the corner that quicken seams to be painting us into. And even better that it will run on my preferred linux platform. Thank you again for your help and time.
Tony
103 Posted by Tony Mount on 07 Feb, 2024 11:15 PM
Hey Stuart, any news on an alpha, beta, whatever? Seems awfully quiet!
104 Posted by dwg on 08 Feb, 2024 01:25 AM
There are no signs of any new Alpha or Beta releases at this stage.
I do not think any of us are expecting any more releases in the 2023 family, so I think it is more likely to be a 2024 release in which case it will be when some new features or significant changes are ready for a more public release. It is worth remembering that any alpha release would be solely for testing purposes
105 Posted by dtd on 08 Feb, 2024 01:44 AM
MD/IK doesn't tend to release any time schedules for their releases.
Stuart, given his expertise, can and does influence fixes and such with the MD development team, though he is "just a user" like many of us.
MD recently released 2023.3(5064) which is extremely likely to be the last release of 2023. Thus, (inferred) MD is working on 2024.0, which if history is readable (from previous times like this) - will likely come out - hmmm, June? (I certainly don't know).
As to preview releases, MD has tended to hold those back so as to make the new year a "surprise" with new features, but this is also always iffy. Like maybe a very few (Stuart... for example) will see an alpha, but it's not as public as "during year" previews.
So, yes, try to wait patiently. A week is way too soon. Think May or June.
106 Posted by Tony Mount on 08 Feb, 2024 01:56 AM
OK. Hope it's not too far into the year! Thanks Stuart.
Thanks dtd also. Maybe we'll file an extension on our taxes!
107 Posted by Stuart Beesley ... on 08 Feb, 2024 08:22 AM
(In the meantime, if urgent, you can use my extract data extension and filter in excel to get your data for taxes….)
108 Posted by Tony Mount on 08 Feb, 2024 11:45 PM
Thanks Stuart. It's already part of the back-up plan. The tax comment was meant to be somewhat in jest. It's kind of tricky transitioning to new software with an operating business, and particularly since I am not the user. There is also a transitional learning curve for my user (aka wife), who has been using quicken for a very long time. So I have to move data and the user pretty much at the same time. We will get through it, but it does make my head hurt sometimes! It will be interesting for sure.
System closed this discussion on 09 May, 2024 11:50 PM.