Why do some fundamentals appear normally on the Fidelity website (earnings included) but are not represented in Wealth Lab? Are the sources for both different? (I wonder why they are different?)

As an example, look at Weight Watchers International Inc, stock ticker symbol WW. (The GICS information is missing too for this particular stock, but that's a separate issue, although it does appear correctly on the Fidelity website.)

Sounds like the issue with earnings is not much different from the one you posted last month or am I wrong?

"earnings per share" not being updated (Fidelity data)

Nobody else seems to have complained.

QUOTE:
Sounds like the issue with earnings is not much different from the one you posted last month

No, this is different. The one I posted last month affects only earnings, but all other on-demand fundamentals work just fine.

This example with WW affects all fundamentals--including earnings. Just leave earnings and the GICS stuff out of it--separate problem--for this new problem unless these other problems are somehow related. Are they? Typically, I see other fundamentals (besides earnings) fine for nearly all stocks. But not in the case of WW. Are you saying you can't reproduce this on-demand data problem with WW? I'm thinking this problem is unique to only certain symbols like WW.

1. Is WW the only affected stock?
2. How does the fundamental data update log look like?

QUOTE:
Is WW the only affected stock?

Well, WW is an extreme case. The only thing coming out of WW is price and volume data. I've seen other stocks like this, but it's rare. Honestly, I can't think of any others at the moment, but I can post examples as I spot them if that would help. Remember, I have small and micro cap stocks in my WL datasets, so I could be more exposed to this problem than other WL users.

QUOTE:
2. How does the fundamental data update log look like?

I'm not using static fundamental updates now. Everything is done on-demand for fundamentals (except "estimated earnings"). A fundamental request hits the following catch statement.

CODE:
Please log in to see this code.

Of course, the next question is what's in the try{...} block? Hmmm.

CODE:
Please log in to see this code.

I don't have a trace handler setup for that catch statement, so I can't precisely say which statement causes the catch execution, but I would suspect it would be one of the earliest ones since I'm not getting anything back from the earliest listed (which are listed in the order of their appearance in the code).

Let me emphasize, this private library code is two years old and works well with nearly all stocks. Even the micro cap stocks, and stock without earnings posted, show many of their other fundamentals without problems.

Thanks for the followup. So the possible issue may be with small/micro cap stock(s).

QUOTE:
The fundamental request hit the following catch statement.

Sorry, what I meant to say is "how does the update log looks like in the Data Manager"? In other words, do you get any fundamental data for that symbol?

QUOTE:
may be with small/micro cap stock(s).

It's true that this category has all the problems; that's normal. Hmm, I just looked up WW on the Fidelity website and it's a small cap stock. I didn't know that; otherwise, I wouldn't have griped about it. Perhaps this isn't that big of a deal then.

It still seems strange to me that these small/micro cap stocks have fundamentals showing up on the Fidelity website, but some of their fundamentals don't show up in WL. Do you have this same problem? Aren't the data sources for both the same?

QUOTE:
How does the update log looks like in the Data Manager?

I'm only using Data Manager (static updates) for "estimated earnings". All other fundamentals are on-demand fed. And WW isn't even in my WL datasets, so it doesn't have any cached data of any type.

QUOTE:
It still seems strange to me that these small/micro cap stocks have fundamentals showing up on the Fidelity website, but some of their fundamentals don't show up in WL. Do you have this same problem? Aren't the data sources for both the same?

Perhaps @Cone may have an idea?

QUOTE:
And WW isn't even in my WL datasets, so it doesn't have any cached data of any type.

I'm pretty sure about the opposite. Whatever you see on the screen gets cached to one of those FidelityFundamental* folders.

QUOTE:
Whatever you see on the screen gets cached to one of those FidelityFundamental* folders.

So when I'm screening for new stocks which are not part of my WL datasets, that on-demand data gets cached anyway? (That's probably a good feature.)

And when you have "Delete data for Symbols not in contained in DataSets" checked in Data Manager, does that FidelityFundamental* folders data then get removed on the next Data Manager update?

I've been thinking about a recursive shell command to delete all *.WL files that haven't been updated for 6 months.

QUOTE:
So when I'm screening for new stocks which are not part of my WL datasets, that on-demand data gets cached anyway?

I believe it does.

QUOTE:
And when you have "Delete data for Symbols not in contained in DataSets" checked in Data Manager, does that FidelityFundamental* folders data then get removed on the next Data Manager update?

No, that shouldn't remove the fundamental data.

QUOTE:
I've been thinking about a recursive shell command to delete all *.WL files that haven't been updated for 6 months.

Been part of a batch file of mine :) "180" is your 6 months:

QUOTE:
rem Clean up old fundamentals

forfiles -p "c:\Users\Windows username\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Data\SomeFundamentalProvider" /s /m *.* /D -180 /C "cmd /c del @path"

I didn't see this before..

QUOTE:
I've been thinking about a recursive shell command to delete all *.WL files that haven't been updated for 6 months.

There's an easier way. Open the Data Manager > Fidelity Data tab > check "Turn on Symbol Management".

If it's already on, you probably already have a big list of symbols in "Quarantine" . Just highlight them and "Delete Symbol(s)". This will remove their .WL data and also delete them out of your DataSets. Be patient with the process - it could take several minutes for some cases.

Re: WW
I updated it today, no problem. All the fundamental data came in back for the last 24 quarters:

CODE:
Please log in to see this code.

If you still have a problem with that one, just delete its WLF file at:
C:\Users\[you]\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Data\FidelityWSODFundamentalProvider\W\WW.WLF

QUOTE:
There's an easier way. Open the Data Manager > Fidelity Data tab > check "Turn on Symbol Management".

I already have that turned on. That setting only applies to price data, but not the fundamental data files.

Go into C:\Users\%USERNAME%\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Data\FidelityWSODEstimatedEarningsProvider\A on your workstation (any fundamental data directory will work), and look at the last modification dates. I think you'll find some a couple years old unless you're running a cron script (I mean Windows scheduler script) to regularly remove them.

Earnings are still coming in late for many small and micro cap stock symbols on WL: ABT CATY GTLS HOMB KSU SKX are some examples for today. It's a regular thing. I'm not sure why. Do you see earnings reported for these on your system today?

The earnings for WW isn't showing up in either the [1] WL fundementals or the [2] EarningDate Community.Component function. It would be nice to see the earnings in one or the other.

Yes, it's a "small cap" stock (as usual), and yes the Fidelity website shows the earnings data as expected.

This has been a problem for some time. It's not new.

Also, when the earnings for a stock is not found by the EarningDate function (let's take HMY as an example), the response from the EarningDate function is very slow; it hangs the Chart window for 40 or 50 seconds. Yes, I can add HMY to the EarningsDateIgnore.txt bad actor's list, and that does work well. But it would be simpler if it was automatically added to the earnings cache as "not found" for a month before it tried to look it up again. Just a thought.

Otherwise, the EarningDate function is a nice product.

The Earnings Date Helper in C.Components is designed to fall back upon a second data source if the first doesn't work:

QUOTE:
GetNext first checks for an upcoming earnings date from earningswhispers.com. If not available, it automatically calls the GetNext2 method, which accesses money.cnn.com for the symbol's earnings release date.

If three different sources aren't showing the earnings for WW, sorry but it looks like you're out of luck.

QUOTE:
If three different sources aren't showing the earnings for WW, sorry but it looks like you're out of luck.

I briefly looked at the EarningsDate code; I understand. The problem is each time I display HMY or WW on the Chart, my Chart freezes up for 45 seconds. If the routine automatically cached the earnings for these stocks as "not found", then it would freeze up once and immediately give up on all other subsequent attempts (until the "not found" condition is deemed stale say after a month or two). That's all I'm suggesting.

Another thought would be to optionally substitute the Fidelity website for one of the other three earnings-date sources. When all attempts fail, the Fidelity website seems to come through okay for US based stocks.

I've looked into the EarningsDate Helper and the two symbols:

WW - works just fine for me.

HMY - The problem with symbol HMY is that it does not have a next reporting date which makes the EarningsDate go into a deadlock. As it will not work with this symbol, the solution is: put HMY on the ignore list (EarningsDateIgnore.txt) as per the online user guide.

---

In this thread, this discussion of the EarningsDate class is complete offtopic. If you have further comments re: EarningsDate class please start a new topic for it and one of us will pick it up from there.

Here let's focus on the subject in your post #1 exclusively: "Earnings missing in WL that appear correctly on the Fidelity website". Thanks.