2011r2(803) loses 'category' for memorized transaction report
If I memorize a transaction report with Account/Category set to a category, Moneydance forgets the category. It displays or edits the report with the account/category set to the first account instead. This broke all my memorized category transaction reports.
To duplicate:
- Tools>Graphs and Reports, select Transactions report, Reset. Pick any Category (not account).
- Click on Generate to display the report.
- Click on Memorize, enter a name, and click OK, then Done to close the report.
- In the reports window, click on Memorized Reports and select the report you just named.
- Click on Edit. Account/Category shows the first available account, not the category you selected for the report.
- Close the reports window and run the memorized report from the home page (or from Reports, Memorized, select the report and Generate). Again, the report will cover all transactions in the first account, not the category you selected.
Note: It works OK with an account, just not with a category. When a category is used, the data file seems to correctly store the report parameters (TxnReport, account=...), but Moneydance seems unable to process it.
Support Staff 2 Posted by Jon Hoover on 12 Dec, 2011 04:49 PM
Hi,
Sorry we did not get back to you sooner.
Thanks for making this aware of it and including clear steps for replication. I was able to recreate it and created a bug ticket for it.
One workaround is if you generate the report and memorize it on the sidebar then this does not happen.
Thanks!
Sincerely,
Jon Hoover, Moneydance Support
3 Posted by ljb on 14 Dec, 2011 02:01 AM
Are you sure about that workaround? Maybe I'm doing it wrong - I'm not sure what you mean by "memorize it on the sidebar". But if I call up the memorized report (created per my steps above) using the sidebar, it still drops the category and shows the first account instead.
Same thing happens if I initially create the report via the sidebar, then memorize it: lost the category.
Support Staff 4 Posted by Jon Hoover on 14 Dec, 2011 02:30 AM
Hi ljb,
I guess I am not so sure. I agree that if you generate the report from Tools -? Graphs and reports then if you access the memorized report from the sidebar then it doesn't work. But I did not have the problem if I selected the report from the sidebar and edited it and memorized it their. I assume you are using the latest version of Moneydance?
Sincerely,
Jon Hoover, Moneydance Support
5 Posted by glewbel on 14 Dec, 2011 03:14 AM
Same problem here... I have created a bunch of memorized transaction reports over the past few years, and they are now useless. They have all "forgotten" the specific categories I chose when I last saved the reports. When I run them from the sidebar, there's no difference from when I run them from the usual dialog box, and I've also tried editing a few of them and memorizing them only from the sidebar. That doesn't work either. I end up with a transaction report that includes ALL categories, not just the ones I selected before I memorized the report. I'm going to have to recreate all of them unless someone can tell me how to get them back as originally memorized.
6 Posted by ljb on 14 Dec, 2011 11:50 PM
Jon, re: version, see subject of this thread.
I tried some more and found out something important I missed. If I use a a top-level, or "parent" category like Automotive (in the default set), it works - memorizes and recalls properly.
If I use a second-level category like Automotive:Fuel, it does not work. The memorized report does not come back with the category - it seems to revert to the first account.
Does this make any sense? I'm think I'm seeing behavior that depends on whether it is a top- or 2nd-level category, not whether I use the sidebar or not.
7 Posted by glewbel on 15 Dec, 2011 12:56 AM
Time is of the essence here. The end of the year is coming and that means generating MD reports for tax purposes. Right now, as everyone knows, the Transaction Report function is somewhere between "unreliable" and "completely broken." MD Support staff, your customers would be very grateful if you would do your best to get this problem solved promptly.
Support Staff 8 Posted by Jon Hoover on 16 Dec, 2011 03:03 PM
Hi,
Thanks for the tip on a correlation with Parent vs. Child level categories. I have upgraded the bug ticket status to major. For the next little while the developers are working hard to get the i-app sync rewrite out on time but hopefully after that they can take a look at this and a few other annoying bugs.
Please let us know if you have any more questions.
Sincerely,
Jon Hoover, Moneydance Support
9 Posted by glewbel on 18 Feb, 2012 11:09 PM
It's been more than 4 months since this bug was reported in this forum, and 2 months since this bug was upgraded to major status. What does that actually mean? Could you please give us a status report?
We're well into tax season now and I've had to re-do all my Transaction Reports as a result of the bug. I'm not happy about that and suspect other users aren't, either.
Please advise.
10 Posted by glewbel on 15 Mar, 2012 11:49 PM
Jon (or anyone at MD who might be tracking this issue), tax season's over for me, and I didn't have any luck getting MD to do what it is supposed to do with transaction reports.
This is what has happened so far: 1) User takes the time to report a bug, 2) MD verifies the bug and upgrades it to "major status," 3) ... there IS NO 3. No fix or patch has been released even though it's been 5 months hanging fire.
Is anyone at MD going to fix this bug before the 2013 tax season?
Support Staff 11 Posted by Jon Hoover on 23 Mar, 2012 03:05 PM
Hi,
Unfortunately I don't have any timeline on this bug. Its currently tagged as major, and more recently the wishlist for our next version but unfortunately its still behind in line for a few other bugs that we are working on.
Sorry for the inconvenience.
Sincerely,
Jon Hoover, Moneydance Support
12 Posted by glewbel on 29 Mar, 2012 05:25 AM
Sorry to hear that, Jon. I don't think that a major bug that cripples one of MD's standard reports belongs on a wish list for a future version. Usually, bug fixes are not requested features. Is anyone else having problems with this, or am I the only one who creates transaction reports that don't work?
Support Staff 13 Posted by Angie Rauscher on 29 Mar, 2012 04:14 PM
Hey all,
Great news! Happily this was a fairly simple bug to run down, and Sean has just fixed the issue in our code, and the fix will be released in our next daily and preview builds. If you'd like to be notified when preview releases are available, please set your Moneydance Updater extension to notify you for these releases. I'll also post on this thread when the next preview (or daily build, which is more error prone but will contain the fix) is released.
Thanks for bearing with us,
Angie Rauscher
Moneydance Support
14 Posted by sth on 05 Apr, 2012 04:39 PM
Angie,
Great to see these bug fixes, but it appears that the nightly builds have not built since March 19th. I think the nightly build script needs a boot-to-the-head to get it unstuck?
The nightly build is 807 and the preview is 805. The latest 807 build is only 23 bytes larger than the 806 build from mid february. The latest preview is from back in December.
Support Staff 15 Posted by Angie Rauscher on 05 Apr, 2012 05:55 PM
Sth,
Our build machine is in the "boot-to-the-head" stage of it's life, and I've asked Sean about getting a new daily out. I'll post here when it's ready. Sorry for the delay,
Angie Rauscher
Moneydance Support
16 Posted by sth on 06 Apr, 2012 03:45 PM
Angie,
I figured that was the case, and has been for awhile. I don't know if it is a hardware or software issue that hangs the boots, but I figure you will get it updated. This is just a way of letting you know that some of use see bug fixes and tweaks and check the nightly builds.
17 Posted by glewbel on 20 Apr, 2012 02:53 AM
Angie, it's been 2 weeks since your last post on this issue, and more to the point, about 6 months since this bug was first reported in this thread.
Could you please let us know when production software without this issue really will be available to all MD users via the normal updater?
Support Staff 18 Posted by Angie Rauscher on 24 Apr, 2012 05:28 PM
Hi all,
This report issue is fixed in the newest daily, just released yesterday, which you can find here. This is a daily testing build, which may people use quite successfully, but you should always be cautious and make sure you have a recent backup. Please let us know how it goes with this report, and any other issues you come across. I'm not 100% sure when this will be available as a full release- we generally test these builds for a while first.
Please let me know if I can be of further assistance,
Angie Rauscher
Moneydance Support