Bug importing price history from csv file for a security not in base currency
This link describes exactly my problem.
The link above references that this is a known problem, but it was closed with no mention of a solution.
Given the fact that the Updater extension has stopped working, I've taken to importing all my security prices as part of my end of year reconciliation. My base currency is in GBP, but all of my investments are denominated in USD. Unfortunately, I've just discovered that all of my imported prices are incorrect as Moneydance interpreted them as GBP. I've tried changing the base currency to USD, import the price history, but when changing the base currency back, it changes all the prices of the securities.
I'm using version 2011r2 (802).
Is there a way to work around this problem?
Showing page 2 out of 2. 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
31 Posted by 1smost on Feb 09, 2018 @ 12:49 AM
Hi Kevin N
Your instructions worked a treat.
It also now appears that the problem of updating security prices in a currency, that is not the system default currency, is now working as it should.
Thanks to all those users who have provided input and assistance and also to Moneydance staff who made the software change.
Cheers
Tony
32 Posted by g on Feb 26, 2018 @ 09:28 PM
@derekkent23 Coming back to reply to your post from Jan 21, 2018 @ 12:16 PM…
First of all, thank you for your help and enthusiasm in trying to address the problem even though you are not support staff and just a user. That is much appreciated.
I misunderstood your two suggestions in the previous post.
Your scenario 1: "your base currency is GBP and all your securities are set to GBP, prices are imported in GBP."
This would indeed eliminate any bugs dealing with currencies. Unfortunately, all the transactions in the account are in USD, so I don't see having all the prices in GBP as a practical option.
Your scenario 2: "your base currency is GBP and the relevant securities are set to USD, prices are imported in USD."
This is my current scenario and to answer your question, this is the type bug that I'm seeing. In fact, I have found two bugs…
Price Import Bug
When loading prices through extension from the Yahoo API, the prices would be converted from USD to GBP and then converted back when displayed in the UI. For example, given 1.25 USD per GBP, a price downloaded of 100 USD would be converted to 80 GBP and stored. When displayed in the UI it would be converted back to 100 USD.
However, I have confirmed that when importing either through the QIF file or the csv file import dialog, the prices are interpreted as the base currency (GBP) rather than the currency of the security (USD). Taking the above example, a price of 100 USD in the file would be interpreted as 100 GBP and saved as 100 GBP. When displayed in the UI it would be 'converted' to USD and show as 125 USD.
Change Base Currency Bug
My first work around was to as suggested elsewhere was to change the base currency to USD, import the prices, and then change the base currency back to GBP. In theory this should work, however, there is another bug when changing base currencies — the high and low prices are converted correctly, but the close price is not preventing this workaround from being sucecssful.
Workarounds
I started to work around these bugs by converting all of the prices outside of Moneydance from USD to GBP and then importing the modified files. I take it that this is where your suggestion of the hleofxquote tool could help — though I didn't attempt to use it. To make this workaround work, the prices used for the conversion outside of Moneydance have to match the currency prices used in Moneydance. I was able to get this working successfully though it took some effort to prepare the files.
Once I fully understood the issues (and decided that converting the files prior to import was too tedious and brittle), I moved on to writing my own extension to import prices from csv files and perform the conversion correctly. Not helpful for others reading this that might have the same problem (sorry!) but I now have something in place that is working for me.
33 Posted by derekkent23 on Feb 26, 2018 @ 10:18 PM
I am not support staff, just a user.
Hi g.
Things have moved on since my post of Jan 21.
Can you confirm you are doing your testing with 2017.7(1665) or later and that the build of the Security Price Loader is 2020?
34 Posted by g on Feb 27, 2018 @ 09:06 AM
Hi derekkent23,
I am using 2011r2 (802).
-g
35 Posted by derekkent23 on Feb 27, 2018 @ 09:23 AM
I am not support staff, just a user.
Hi g.
Sorry I should have remembered that from your first post.
I think the issue you are having has finally been fixed in the latest preview build of Moneydance see change log at http://infinitekind.com/previewdl/current/changelog.txt
If you are happy with your own solution great. If, however you want to move forward you can get a 50% discount on 2017. You could try downloading the preview build, without making a purchase, into a separate account on your computer to test. You could also try the Q & ER extension or as I prefer use the stand-alone Q & ER and then import its output into Moneydance using the Security Price Loader extension.
Hope this helps
System closed this discussion on May 29, 2018 @ 09:30 AM.