Equity Summary Score doesn't display in chart
Author: jeffjs2003
Creation Date: 5/10/2018 4:25 PM
profile picture

jeffjs2003

#1
I'm unable to get Equity Summary Score to display in a chart.

1. I've checked and updated all six Fidelity Fundamental Data categories including ESS.
2. Enabled ESS in Preferences prior to update.
3. Tried multiple symbols.
4. See png below.
5. Chart bars are Daily and range is 23 months.
profile picture

Eugene

#2
Please try to reopen the chart prior to plotting any fundamental item after updating it the way you've described. Try a different data range (All Data) and a different symbol. If no go the ESS data may be unavailable at Fidelity.
profile picture

jeffjs2003

#3
I've tried the things you suggested with no luck. The ESS data is accessible from Fidelity at both their website and trading platform, Active Trader Pro. How best to proceed?

Just to clarify: Although I can retrieve limited ESS data from Fidelity directly, I'm unable to access it from Wealth-Lab.
profile picture

jeffjs2003

#4
I contacted Fidelity today and they were able to successfully plot ESS in Wealth-Lab right away while I was on the phone with them.

1. Their version is the same as what I'm using, 6.9.19.0
2. They were able to plot ESS with multiple symbols and Date Ranges.
3. We compared our Preferences to see if there was any discrepancies but didn't find any.
4. As far as accessing data is concerned, the person I spoke with (Tyler) said that he had the same permissions set up as I do.

As far as getting ESS to display for me, the only suggestion they had was to uninstall/reinstall Wealth-Lab. I know that you guys frown on that as a remedy so I'm wondering how best to proceed? Does ESS (from Fidelity) work on your end?
profile picture

Eugene

#5
Jeff, thanks for the update. So what we know now is that ESS data is still supported. If you physically remove the entire ESS data subfolder under Wealth-Lab's Data folder and update your Fidelity fundamental data again, what would the data update log show?

It's here (can't tell you the exact subfolder name as I don't work with WLP):

C:\Users\Windows User Name\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Data\..
profile picture

jeffjs2003

#6
I deleted the EquitySummaryScoreProvider folder from the data directory and updated Equity Summary Scores which recreated the folder again. Still no ESS plot. See attached updated log file below.
profile picture

Cone

#7
You have saved, closed, and re-opened that Strategy Window, right?

The only scenario that I can think of is that you created the plots and subsequently updated the data. If so, it's possible (although I think not likely) that that window won't be aware of the "non-static" data.
profile picture

Eugene

#8
What Cone has mentioned is even a live bug:

(177409) Fundamental items plotted before acquiring the data can't be refreshed until the chart is reopened
profile picture

LenMoz

#9
From my vantage point...

Yesterday evening I refreshed my ESS data. I made a New Chart and dragged Fidelity fundamental item, "equity summary score", onto it with default parameters. Here's what I noticed among popular symbols...
1. Many symbols have no data (AAL, FOXA, GOOGL)
2. ESS data ends 3/1/2017 (ADBE)
3. ESS data that ends at 10/1/2017 (AMAT, CSCO, GILD)
4. ESS data that ends at 1/1/2018 (CELG, QCOM)
5. ESS data that ends on another date, always the end of a month (ADP, ADSK, AMZN, AVGO, CHKP, CTXS, EBAY, FB)
6. Some symbols are up to date (AAPL, ADI, AMGN, CERN, CMCSA, FAST)

Because, when the data ends prematurely, it's always ends at the end of a month, I suspect a Fidelity or Fidelity Loader issue.

FWIW,
Len
profile picture

superticker

#10
I have "equity summary scores" selected for "Chart Annotations" in WL Preferences, and these annotations always show up for me on the PricePane without problems. But I haven't tried accessing equity summary scores through the "fundamental item" mechanism at all (GetFundamentalItem, FundamentalDataSeries, FundamentalDataSeriesAnnual), although I regularly access many other fundamental items through this mechanism with good success.

So my "guess" is there may be some issue with retrieving equity summary scores via the fundamental item mechanism, but other all functions work as expected. Or perhaps this problem is isolated only to fundamental drag-and-drop indicators, which I haven't used.

Honestly, I didn't even know there was a drag-and-drop indicator for equity summary scores. Why would you need that if they are already enabled in Chart Annotations? (rhetorical)
profile picture

LenMoz

#11
Either way, superticker, the data ends early. See attached...



QUOTE:
Why would you need that if they are already enabled in Chart Annotations? (rhetorical)

... and I didn't know ESS could be seen through "Chart Annotations."
profile picture

superticker

#12
Strange. I can't reproduce your problem with the equity summary scores. Mine show up fine in the attachment. I can't explain it.

I just tried reproducing the equity summary scores problem with a plain chart, but everything looks as expected. Weird. I wonder what's special about 2/28/2017 when the first missing score fails to appear? It's not a leap year (or leap day). Perhaps we update each night at a different time. I update static data just after midnight central US time. But I still can't explain why 2/28/2017 is special.

profile picture

Eugene

#13
Jeff, your update log is suspiciously full of 0 scores being downloaded for active symbols. Something is probably going on at Fidelity side:

QUOTE:
0 new Scores added.
Updating .MID,.NYA,.OEX,.SPX,.STI.A,.STI.N,.STI.O,.XAX,AA,AAP ...
0 new Scores added.
Updating BWLD,BWXT,C,CA,CAG,CAT,CATM,CBPO,CBS,CBU ...
0 new Scores added.
Updating DTV,DVN,EA,EBAY,EBIX,EBS,EEFT,EFX,EMC,EMR ...
0 new Scores added.
Updating KALU,KAR,KFY,KLAC,KMX,KO,KRFT,KS,KSU,LBTYA ...
0 new Scores added.
Updating PBA,PBH,PCAR,PCLN,PEP,PFE,PFGC,PG,PKG,PM ...
0 new Scores added.
Updating PMCS,PNFP,POOL,POWI,PRA,PSMT,PVH,PWR,QCOM,QLGC ...
0 new Scores added.
Updating QVCA,R,RDN,REGN,RFMD,RHI,RJF,RLI,ROG,ROST ...
0 new Scores added.
Updating YHOO,YUMC,ZMH ...
0 new Scores added.
profile picture

jeffjs2003

#14
Cone: Yes, I've closed everything down , updated all the Fundamental Data, and then opened a new chart and draged in ESS. I've done this multiple times with no success.

Eugene: Yes, the 0 scores do look suspicious. As LenMoz pointed out, he too found many symbols that have no data. When I was speaking with Tyler at Fidelity today he was able to retrieve ESS for multiple symbols. It could be that he got lucky when randomly picking symbols. He retrieved AAPL data so I've been using that as a known viable ESS symbol while also trying others.

In spite of all the 0's there was still lot of data; one would think that I should've stumbled onto at least one symbol that was able to plot ESS. Not so.

It looks like superticker and LenMoz are able to plot ESS but with different results for the same symbol and dates. Maybe all three of us have different contents in our EquitySummaryScoreProvider folders? Would it make sense to exchange folders (or use a common one) to see if different results are obtained?
profile picture

LenMoz

#15
My ESS "Update log" is similarly strange...

profile picture

superticker

#16
QUOTE:
In spite of all the 0's there was still lot of data;...
So why is that? Do you have the check box for "Automatically update data for symbols on-demand when they are charted or accessed." checked in the Update Data tab of Data Manager? I do, and I don't have problems.

I think where this is going is that there's some kind of Data Manager configuration difference between my settings (which are working) and those with problems. Perhaps we need to run a "differences check" on our WealthLabConfig.txt files for at least the Data Manager part of it. Attached is part of my WealthLabConfig.txt file. (Some deleted parts are private.)

QUOTE:
Maybe all three of us have different contents in our EquitySummaryScoreProvider folders?
So you're suggesting if you delete those folders and let WL recreate them all your problems go away? Is that really true? Or is the last-value index directory for those folders located somewhere else in another Data Manager file, which is the real problem? I'm thinking it's the latter.

My "guess" is that 2/28/2017 is a special day for LenMoz (when his system stopped receiving summary score updates for ADBE) because he had a system crash on 2/27/2017. He can check his system logs to confirm that.
profile picture

jeffjs2003

#17
QUOTE:
Do you have the check box for "Automatically update data for symbols on-demand when they are charted or accessed." checked in the Update Data tab of Data Manager? I do, and I don't have problems.


No, I didn't have it checked. I enabled it and now I'm able to plot ESS for every symbol I've tried thus far.

I unchecked this option a while ago because it was causing some problem that I don't remember. I seem to recall that in the forum, either Cone or Eugene recommended disabling this feature in order to circumvent unwanted behavior of some sort. I do remember it fixed my problem so I left it unchecked. I'll have to go back and research this again. If anyone has info on this please feel free to chime in. Thanks for all your help.
profile picture

superticker

#18
QUOTE:
Do you have the check box for "Automatically update data for symbols on-demand when they are charted or accessed." checked in the Update Data tab of Data Manager?
QUOTE:
No, I didn't have it checked. I enabled it and now I'm able to plot ESS for every symbol I've tried ...
This may be bad news for us....

What you're telling us is static equity summary score data is failing to be downloaded, and that checking this automatic option hides that fact. :(

What I would tell the WL developers is to check the date stamp on the indexing file for equity-summary-score data files upon WL startup. If it's stale (like after there's a WL or Windows system crash), then WL should rebuild that indexing file from scratch from all the individual data files.

Now I finally understand why so many equity summary scores don't get updated during the static Data Manager update. :(
profile picture

Eugene

#19
Fundamental providers which update data per symbol typically don't keep records of the last update time for a symbol in an "indexing file". The only exception known to me is the Wealth-Data static provider. What they really do is reload the fundamental items from scratch on each request. While I'm not familiar with the ESS provider's way of operation, I'd presume that it's the batch request that may fail on Fidelity end for some reason while single-symbol on demand requests are guaranteed. This, in my opinion, might be the reason rather than an "indexing" failure.

Let's gather some evidence to prove or disprove this theory. I've got a step-by-step procedure on hand using two methods for troubleshooting. They should let us see if server returns empty ESS data for batch requests or give an insight into WLP's possible failure to parse the otherwise valid data. (I'd go for empty ESS data for batch requests, though). As they may accidentally collect some private data in logs (which we'll try to avoid), I'd suggest anyone interested to create a support ticket. Thanks.
profile picture

superticker

#20
QUOTE:
Fundamental providers which update data per symbol typically don't keep records of the last update time for a symbol in an "indexing file". What they really do is reload the fundamental items from scratch on each request.
And I "think" this may be also happening with equity summary scores if "Automatically update data for symbols on-demand ..." is checked as well. But if it's not checked, then it may be (Yes, we can't say for sure.) relying on static cashed data, which may not be there. This would explain the differences one WL user sees verses another.

What we do know is:

1) It's not a server-side only problem; otherwise, everyone would be seeing the same behavior.
2) The problem is not isolated the the individual equity summary score data files; otherwise, when jeffjs2003 deleted all of them and WL recreated them, all his problems would go away. They didn't.

So there exists some third party file on the WL client side that jeffjs2003 failed to delete that causes his problem to persist. I call it a static data indexing file, which points to the last equity summary score update for each individual stock data file. You might call it something different. But its there, and it's unique to each WL user thereby creating the behavior differences we see between WL users. I would ask the developer what the name of that file is so we can delete it and WL can recreate it resetting the unique problems each WL user has with "would be" static equity summary score data.

But I agree, we don't fully understanding what's going on. On the other hand, the developer might.
profile picture

Eugene

#21
I'm pretty sure that this is due to something like a recently introduced server-side issue where a server is aborting batch requests or returning empty data at random.

I have a procedure to clear away those speculations like "static data indexing file" (an extraneous concept to the Wealth-Lab data provider modus operandi.) We successfully used it before in private to revive a broken data feed with undocumented API. Anybody interested is welcome to create a support ticket for further instructions.
profile picture

Eugene

#22
@jeffjs2003, LenMoz

Jeff, Len: would you guys be interested in helping us reproduce the issue and find the culprit? Thanks.
profile picture

LenMoz

#23
Eugene,
The ESS loader isn't working at all for me, and the log is misleading. While it claims "654 new Scores added.", for instance, no data is saved. All the .WLF files, for all symbols, are exactly 12 bytes long. A hex dump looks like this...
CODE:
Please log in to see this code.


I do get ESS data if auto-downloading is checked.

Aside: I concluded years ago that ESS had little correlation to future performance.
Len
profile picture

Eugene

#24
Len,

"On demand update" may be a fix but superticker's able to get the data without activating it. The raw data flows in correctly for him. At least this is what I've discovered in private.

It might help Fidelity to work on a fix it if we capture the raw output for broken downloads, whether they're falsely claiming "654" or "0 new scores added". This is what my troubleshooting procedure is designed for.
profile picture

Eugene

#25
Thanks to everyone who submitted information for troubleshooting in private. What we know by now:

* The raw data returned by ESS server for single-symbol (on demand) and bulk (Update DataSet/All Data) requests are not different. Their XML file structure is identical. ESS server supplies valid data in both cases. We haven't registered any empty records or unexpected input.

* While bulk data requests appear valid, it's still unexplained why only single-symbol requests succeed in Wealth-Lab at the moment. The only conclusion that comes to mind is: WLP has trouble correctly saving ESS data in batch mode (i.e. Update DataSet or Update All Data).

* This is a static data update problem. Activating "Update data on demand" is the workaround.
profile picture

jeffjs2003

#26
QUOTE:
would you guys be interested in helping us reproduce the issue and find the culprit?

Yes. I just submitted a support ticket.
profile picture

LenMoz

#27
Was this ever resolved? I'm guessing "no." Bulk updates still fail for me.
profile picture

Eugene

#28
Sorry, not fixed yet. Thanks for the heads-up!
profile picture

superticker

#29
A couple days ago I deleted all of my static data cache, including the summary scores folder, and now all the summary scores are loaded each day as shown in Post# 15. But in spite of these huge daily downloads, the *.WLF summary score files look like Post# 23, a few bytes long.

Meanwhile, I'm trying to decide what to do until this is fixed. I suppose I should disable static downloads altogether for summary scores.
profile picture

Eugene

#30
QUOTE:
I suppose I should disable static downloads altogether for summary scores.

That's the workaround suggested by the Open Issues page:

Batch update of ESS fundamental data are broken (updates only first symbol in a batch). To be fixed in WLP 6.9.21
This website uses cookies to improve your experience. We'll assume you're ok with that, but you can opt-out if you wish (Read more).