nav[aria-label="Primary Navigation"] { padding: 0; & ul { list-style: none; width: 100%; display: flex; flex-direction: row; justify-content: start; align-items: start; gap: 30px; padding: 0; & li { margin: 0; } & ul li { list-style: none; } } }

Wrong Fund name for Vanguard S&P 500 Growth ETF

cyberphile

I just opened a position in the Vanguard S&P 500 Growth ETF (VOOG). Quicken R65.29 reported the name wrong. It added the security as 20Vanguard SP 500 Growth ETF (see below). It should have been Vanguard S&P 500 Growth ETF. The connection to Vanguard still uses Direct Connect.

I downloaded a QFX file to try to determine what Vanguard might be sending as the security name. It sent:

It appears the S&P string confused Quicken.

Find more posts tagged with

Comments

NotACPA

Had you created the security, in Q, before the download?

Because I have several securities in Q with an & in the name and the & shows correctly.

Also, I just added VOOG to my security list and it shows correctly.

And, even if it were the &, that wouldn't explain the 20 before the security name in your list.

cyberphile

No, the security was added to Quicken upon download via One Step Update. Also, this was Quicken Classic R65.29.

cyberphile

I can reproduce the behavior by creating a fresh, empty, data file and adding just my Vanguard accounts.

NotACPA

But if the security was added to Q before you downloaded it … doesn't that make the name a typo?

And S&P is proper HTML coding for S&P, since the downloaded file is HTML compliant.

And note that there's no "20" before "Vanguard" in your download example.

SO, why can't you do a simple TOOLS, Security List, click on the Security name, click EDIT DETAILS and change it?

cyberphile

I used the information from the QFX file as what Vanguard might have been sending to Quicken. And, yes, in that file that is the correct HTML encoding for an ampersand. However, I forgot that the connection type to Vanguard is still Direct Connect and there is an OFXLOG.txt file that shows what Vanguard perhaps actually sent for the name of this security and it is what shows up in the security list.

I can't say if Quicken Classic interprets what Vanguard sent and created the wrong security name in this log or if this is literally what Vanguard sent. Since there is nobody at Vanguard on the weekend, I'll bring this up with their customer support too on Monday.

NotACPA

Using Direct Connect, the FI is SOLELY responsible for the content of the download, and Q accepts what's sent.

But you never explained why you can't simply edit the security name to what it should be.

A great many of my investments are Fidelity funds … and in Q I have GREATLY shortened names for them … for example not using the "Fidelity" name that pre-fixes all of their funds and also not using the word 'Fund".