Note: Due to abuse of the open system we've had to limit anonymous access. To post a bug report or feature request, please sign up for an account using the Register link below.

Ticket #1263 (new defect)

Opened 1 year ago

Last modified 11 months ago

Download from Hewitt fails to recognize previously established securities (Build 579)

Reported by: dockwpk Assigned to: sreilly
Priority: critical Milestone: Moneydance 2007
Component: onlinebanking Version: 2007.stable
Keywords: online banking, securities Cc:

Description

Build 579 fails to recognize previously established linkages between securities as set up in MD and as downloaded from Hewitt Associates. Falling back to MD 562 resolves the problem. Build 579 shows the unrecognized securities as numbers (e.g. 16420100), while older build used to show unrecognized securities by name. I'm back to build 562 for the time being.

Change History

10/14/07 10:58:20 changed by toddb

I am having similar issues with build 582 and earlier. Securities are defined under "Tools->Edit Securities" and then added to the appropriate account using "Actions->Add Security". When downloading transactions from Fidelity Investments the "Please choose the security that matches..." pop-up appears, but the securities that I defined in MD for this account are not available in the drop-down list.

Unfortunately, I did not take note of the build where this issue first appeared.

11/18/07 18:02:07 changed by g

I have had this problem with Ameritrade since I started using Moneydance (see #1126). It was only a minor nuisance though because I could just hit "Cancel" on the dialog. However, now with r584, there is no cancel button. This means that I am forced to select "None of the Above" which then inserts duplicate securities every time I download transactions.

Sean, if this issue is related to the broken CUSIP information (as in #1126) is there any way that I can capture the data from Ameritrade (in my case) to help you debug this? If the CUSIP is in fact bad, certainly it isn't the "fault" of Moneydance, but Quicken didn't have this problem, so there must be a way to work around it.

Here are some of my thoughts. It seems that at times the CUSIP is valid and other times it isn't for the same security. I know that Moneydance now validates the CUSIP and stores it in a broken-CUSIP tag. If both of these tags could be stored on the same security and both could be used for matching, that might solve the problem. If a match isn't found, the dialog would just need to include the appropriate securities based on if the CUSIP is valid or not. For a valid CUSIP, include all securities without a CUSIP. For an invalid one, include all securities without a broken-CUSIP tag.

This of course assumes that if a security has a broken-CUSIP that it is always the same in the downloaded data -- not sure if that is the case or not. To avoid this assumption, simply include the entire list of securities in the match list if the CUSIP is invalid and just replace the broken-CUSIP tag if one already exists on the selected security.

In any case, I hope this makes sense. Please let me know if there is anything I can do to help with this.