Portfolio Report / Request for Support
I've submitting this question to support via email and private discussion and have not heard back. I'm hoping someone else has had this some problem and can help me out. Sorry I can't attach the screenshots anymore.
Thanks
I’m having problems with the “Portfolio” report in Moneydance. The dollar amounts are correct, however the percentages are wrong. In the attached reports, if you look at the ‘% Change’ in the portfolio review – investment account screenshot, it shows a change of –41.93% for Powershares Clean Energy ETF. However, in the report view, it shows it is down 232.13%, which makes no sense, as this is a long equity position and it’s not possible to lose more than 100%. I’ve had this problem with the portfolio report for some time (I’ve actually never used it, and relied on my brokerage reports). I’d like to be able to use moneydance for reviewing my portfolio performance.
I’m running 2011r2 (803), which the updater extension states is the most current version.
I submitting this question on 3/4 via email, but have not heard back. I can only attach one file to this discussion, but the email contains all screenshots.
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
1 Posted by Scott Meehan on 21 Jun, 2012 04:29 PM
Hi Will,
I'm sorry for our extremely delayed response! Somehow your post slipped through the cracks.
Are you still having this issue? If so, please let us know and we will work to diagnose them. Also please resend the screenshot(s) because we did not receive them.
Sorry again for our delayed response!
Scott Meehan
Moneydance Support
2 Posted by will on 25 Jun, 2012 05:55 PM
I had several open tickets about this matter as I was not getting a response via email or the private ticket - although Tom Freeman eventually provided a response to my private ticket. He stated it was a known bug and they were working on resolving it for a future release. Is this still the case? Thanks
3 Posted by Ben Spencer on 25 Jun, 2012 11:09 PM
This is a duplicate post from the same user about a known issue.
I recommend that before responding to an old case click on the user name to see the other posts they have made just in case it is a duplicate.
4 Posted by Ben Spencer on 25 Jun, 2012 11:10 PM
I am closing this thread to consolidate the topic into a single thread.
Ben Spencer closed this discussion on 25 Jun, 2012 11:10 PM.