- ago
AAPL, FB, and KHC are not updating as of 7:35 PM EDST. All other NASDAQ 100 symbols updated around 5 PM.
0
1,280
9 Replies

Reply

Bookmark

Sort
Cone8
 ( 4.98% )
- ago
#1
Edited....
0
Cone8
 ( 4.98% )
- ago
#2
They're updated. Can't say why you're having trouble with it, but trying clicking the "Loaded" message in the lower left status bar of the Strategy window. And if that doesn't help, try updating the DataSet with the Data Manager, or finally restart WL7. Let us know what worked for you!
0
Cone8
 ( 4.98% )
- ago
#3
Hmmm, I just checked using WL7 myself, and you're right. WL7 isn't updating all the Wealth-Data symbols. The data are there, so we'll look into it!
0
Cone8
 ( 4.98% )
- ago
#4
Actually, in my case, it's "OK", but the behavior is hard to get used to. Because of the Weath-Data dynamics, if you update the Dow 30, you'll be sure to update only the current Dow 30 components. Other symbols that have left that index won't be updated for a Dow 30 update, but could be if you update the S&P 500, for example.

Anyway, this doesn't explain your AAPL, FB and KHC in the Nasdaq 100 - they should update with that DataSet.
0
- ago
#5
@sdbens20

When a stock isn't updated, what happens if you go to Historical Providers tab, right-click Wealth-Data and choose "Clear Internal Request Tracking Info"?
0
- ago
#6
I had a similar problem. I fixed it this way:
- Create a dummy strategy and set its data Scale to whatever you need (in my case 5-minute).
- Set Date range to multiple years.
- Then backtest the strategy on the dataset. This will force all symbols to be updated.
0
- ago
#7
All symbols are up to date this morning without me doing anything. I'll let you know if I see this again. Thanks.
0
Glitch8
 ( 10.62% )
- ago
#8
It is probably due to the built-in logic we have to control repetitive update attempts, which just bog down the data loading process. In Build 4 I added some logic to overcome that in Data Manager, DataSet update to let's see if that helps eliminate the problem going forward.
0
- ago
#9
Will do. FYI -I tried closing and reopening WL last weekend and that did not clear the problem. Also rebooted computer.

Thanks.
0

Reply

Bookmark

Sort