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; } } }

What is the Source of Pricing Data for Unusual Symbol?

allen_car

I have a New Hampshire 529 at Fidelity owning a single fund. I also have 8 other Fidelity Investment Accounts using the same Direct Connect log-in. The 529 fund has a symbol that is an unusual format; NHFSTMX97. The pricing only updates through a Direct Connect update from Fidelity and not when a Quicken Quotes Update is performed. This is what I would expect for a proprietary symbol; but Fidelity is claiming that the pricing data comes from Quicken. A google search for NHFSTMX97 does not return any pricing data. Does Quicken provide the pricing data for NHFSTMX97 or does it come from Fidelity?

The problem is that data downloaded associates the closing price of the fund NHFSTMX97 with the wrong date though out the week. But it does correct the error for the Friday data if a Fidelity Direct Connect download is done on Saturday. There aren't any problems with any of my other investments.

I have used Quicken for 28 years and have followed my investments in over 600 Securities; so this is not a beginner's problem.

Find more posts tagged with

Accepted answers

Chris_QPW

Non publicly traded security prices come from the financial institution when you download the transactions.

All comments

allen_car

I forgot to provide what Version of Quicken I am using: Quicken Premier, Version: R36.38; Build: 27.1.36.38; running on Windows 10 Home (fully updated).

Chris_QPW

Non publicly traded security prices come from the financial institution when you download the transactions.

allen_car

Chris, Thank you for your clear answer. That is exactly what I have been trying to tell Fidelity. I guess I will try a 3rd time to make them understand the problem is theirs.

Chris_QPW

allen_car said:

Chris, Thank you for your clear answer. That is exactly what I have been trying to tell Fidelity. I guess I will try a 3rd time to make them understand the problem is theirs.

You might want to show them your OFX logs, especially the section with the prices/shares.
Do an update of only the Fidelity account (it will do all the Fidelity accounts at once) that way the Send/Recv for this will be at the end of the log:
Help -> Log Files -> OFX Log

Here is an example. Note that I ran this through a formatter, lots of times this will be all on one line (search for your security).

<SECID>

<UNIQUEID>27828Y108

<UNIQUEIDTYPE>CUSIP

</SECID>

<SECNAME>EATON VANCE TAX MANAGED BUY WRITE OPPORTUNITIES FUND

<TICKER>ETV

<UNITPRICE>16.68

</SECINFO>

<YIELD>0

</STOCKINFO>

allen_car

Thank you for those details. When I was doing my troubleshooting within Quicken; I was separating each Financial Institution and the Quicken Quote Update into a different update steps so that I could observe the changes.

I know very little about QXF Log files; I did not know where or how to look in the QFX Log. Your comments will be very helpful in clearing up and reducing the size of the file to send them.

Have a good weekend.

Chris_QPW

If you search backwards from the end of the log file for SEND that line is the start of what Quicken sends.
Then if you search from there for RECV that is the start of what the financial institution returns.

allen_car

Success. I have been able to find the most recent data for NHFSTMX97 (even though it is in the very compact unformated text) and understand the meaning of the different data-variables NHFSTMX97<UNITPRICE>45.6200000<DTASOF>20211119033009.000[-5:EST] meaning Unit-Price = 45.62 & Day-Time-As-Of="11/19/2021-Time of update Unsure".

Is there a way to reduce the size of the QXF Log? Mine is huge (2.7MB for a txt file); printing would result is over 1200 pages of text covering every page.

Again, thanks for helping.

Chris_QPW

20211119033009.000[-5:EST]

Date: 2021-11-19 (formatted year, month, day)
Time: 03:30:09.000 3:30:09 am. (the hours are for a 24 hour clock). .000 no fractions of a second.
-5 hours offset from EST.

As far as the OFX log goes that Quicken is displaying it is in fact the *OFXLOG.DAT file stored where your data file is. There is also an old version of it there. This is a "scrambled" version of the log file. When you open it in Quicken, it unscrambles it. It is scrambled so people can't read it from outside of Quicken because it contains sensitive information.

You can delete these if you like, but the next time you do an update they will just get recreated. They cycle the current one to the old one over time and finally out of the old one, so they don't get much bigger.

As for the OFXLog.txt file you can of course trim it down for the purpose of looking at just what you want or printing and just save that.

Chris_QPW

Actually I got the -5 offset wrong. The time is given in EST. The -5 hours is the offset for EST to UTC (Coordinated Universal Time, also known as GMT).

allen_car

Chris, Thank you for all the attention you have provided. I learned a lot. I can now identify and understand most of the variable names and the values stored in the data exchange from Fidelity. It's reasonably easy when I slow down and look at the data details; versus get overwhelmed by the large block of unformated text that you initially see. I will put together a plan to minimize the updates and only perform them when the mismatched data to readily identifiable in the QXF Log (plus I will highlighting the problem areas for them to see in a separate, shortened, edited file).
Your comment about the QXFlog.DAT being normally scrambled, eliminated my worries because I was able to find all the unencrypted account numbers in the log. I will need to delete any unscrambled logs when finished.
Yes I expected that the timing would have been based on GMT since all connected devices must work on the same time reference. I was being lack in not keeping track of my last update time; so I could not identify the corresponding time elements in the number string.

Chris_QPW

You misunderstood what I was saying about the DAT file.
Here is a screenshot of what I have my data file:

Image: https://us.v-cdn.net/6031128/uploads/editor/z2/rww03b218yyc.png

The name of my data file is Current.QDF as you can see. The OFX log file is CurrenOFXLOG.DAT, and the older one is CurrentOFXOLD.DAT. If you open one of these this is what you will see:

Image: https://us.v-cdn.net/6031128/uploads/editor/cv/gmtlgjy2rzgh.png

This is the "scrambled" copy of your OFX log file. It is the place Quicken stores this log information.

Without Quicken and your data file, this is what anyone trying to read it would see.

Now once you open your data file and do Help -> Log Files -> OFX Log, Quicken descrambles the log file and shows it to you, and you can save it to OFXLog.txt. This is the unscrambled version and you should be careful who has access to it because it does have your account numbers and usernames in plan text in it. Note that the passwords have been removed.

Chris_QPW

Just for reference here is the website of the group that maintains the OFX standard:
https://financialdataexchange.org/ofx

Select The Specs and you can download it.
The direct link is: https://financialdataexchange.org/common/Uploaded%20files/OFX%20files/OFX%20Banking%20Specification%20v2.3.pdf

The main reason I didn't mention it before is there is a ton of information in it.