Security price history window bug 2017.5(1639).

derekkent23's Avatar


18 Oct, 2017 08:06 AM

Every three months or so I use the Extension “Security Price Entry” and the third-party Extension “Security Price Loader” from

I have found a bug in Moneydance, which I don’t think existed the last time I used these extensions. So, the bug has crept in on a resent build of Moneydance. I don’t think the bug is in the extensions.

In both extensions you can set the Date that the security prices entry should have in the security price history after the extension is executed. When executing both extensions if a price already exists on that date the new price is set for only the current price is updated. It took be ages to work out why after running the extension my investment totals were wrong. I then had to open each of my 46 security history price windows and manually update any dated prices that existed before the extension was run that had the same date as used in the extension.

Can it be fixed?

  1. 1 Posted by Dan Hanger on 18 Oct, 2017 12:05 PM

    Dan Hanger's Avatar

    Is this the same thing I wrote about here:

    Sounds similar.


  2. 2 Posted by derekkent23 on 18 Oct, 2017 12:51 PM

    derekkent23's Avatar

    I am not support staff, just a user.

    I believe it is the same issue.

    If a dated price already exists then using an extension to enter a new price with the same date or on the same day will not update the dated price only the current price.

    I consider this to be a bug.

    Support can you look into this please?

  3. 3 Posted by Henry on 18 Oct, 2017 03:52 PM

    Henry's Avatar

    Hi derekkent23 and Dan,

    I've tested and reported the issue to the lead developer, I'm currently waiting for a response.
    I will inform you as soon as I get any update.

    Thank you for posting the issue and for the great description.

    Infinite Kind Support

  4. 4 Posted by derekkent23 on 23 Oct, 2017 05:04 PM

    derekkent23's Avatar

    I am not support staff, just a user.

    I got a message from Sean the lead software developer that the bug has been fixed in build 1646
    Change log reads “fixed bug that prevented changing the rate for an existing currency or security history entry via the API (such as the Security Price Entry extension)”
    Downloaded this preview build from
    Tested this build and it works for me.

    Great work Sean.

  5. 5 Posted by Dan Hanger on 23 Oct, 2017 05:16 PM

    Dan Hanger's Avatar

    That was fast. Thank you.


  6. Henry closed this discussion on 24 Oct, 2017 12:58 PM.

Comments are currently closed for this discussion. You can start a new one.

Keyboard shortcuts


? 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