I'm re-opening:
I have upgraded to R67.10 and now it seems the Early Access feature has disappeared and I can no longer use the 'old' report interface. Has there been any progress on re-creating the bug I previously reported?
Hello @DistressedParrot,
Thank you for reaching out again. I'm still not able to replicate the issue you're reporting. Since you said (in the previous discussion) that you see the same issue in a test file, the next step is program troubleshooting. To troubleshoot program issues, please try reinstalling the current update patch manually. To do that, please follow the instructions in this article: https://www.quicken.com/support/update-and-patch-20182019-release-quicken-windows-subscription-product/#section-windows-2
P
Hi Kristina,
Yes I tried reinstalling the patch. I’ve also tried the same data file on a different computer. The Quicken bug with not correctly reporting non-base currency values when a report selects a non-base currency is still there.
Is there a way I can upload my Quicken data file to you so you can reproduce the bug? It’s a small file that has a handful of transactions and accounts and I’ve already uploaded it a few times thru the quicken for windows program bug report feature but haven’t gotten any responses to date on that path.
One workaround suggestion for others reading this: it’s a hack, but if you set the current exchange rate for base currency to foreign currency to 1.0, then the reports will show the proper foreign currency amount. In my case I normally use USD for base currency and EUR for the foreign currency but I have tried CAD and it behaves similarly. Eg set EUR:USD to 1, then all the transactions in the EUR-denominated accounts will show the euro amounts.
One other item of note for my older data file vs a file created more recently, newer files appear to have dozens of different currencies whereas my older file has far fewer. I didn’t count them, but I’d guestimate 10 currencies vs maybe 40.
Thank you for your reply,
Based on what you shared in this discussion and what @MyronD shared in the other, similar discussion, it seems like the common factor is that the currency list has been edited.
To test, I deleted several currencies from my Quicken file, then ran a report. Switching to CAD caused it to show no currency in the report header. Switching to USD caused it to display an incorrect currency (and always the same one).
I forwarded this issue to the proper channels for further investigation and resolution. If you would like to contribute to the investigation, please navigate to Help>Report a Problem and send a problem report with log files attached.
Is there a way I can upload my Quicken data file to you so you can reproduce the bug? It’s a small file that has a handful of transactions and accounts, and I’ve already uploaded it a few times through the QuickBooks for Windows program bug report feature but haven’t gotten any responses to date on that path.
When you send a problem report, you typically will not receive a direct response. To clarify, while you do not receive a response for problem reports submitted through the program, these submissions do go directly to a database that is accessible by members of our Product and Development teams, escalation teams, and other internal support channels.
Thank you!
(CTP-17613)
Thank you! That’s wonderful that you were able to recreate the problem by editing your currency list.
To clarify two points:
You do not receive a direct response when you use the report a problem tool. These reports are reviewed daily to track multiple reports of the same trending issues and/or for troubleshooting/escalation purposes. When multiple reports of the same issue are received, those reports are also investigated further. Reports that can be replicated or verified are then submitted as tickets to the proper channels.
You're not the only one who is frustrated with problem reports being a one-way process. There's an Idea post requesting tracking numbers for problem reports:
If that's something you'd like to see added, please add your vote and a comment. Ideas that get enough votes may be implemented in the future!
Considering the age of the original file, it's quite likely that the currency list has changed over the years, and triggered the same issue.