Bars.HasNamedDataSeries return false in 6.2 (resolved)
Author: wbzhang
Creation Date: 6/24/2011 11:06 AM
profile picture

wbzhang

#1
I have some strategies that work fine in previous Wealth-lab (6.1 and before). But now I cannot run them with WL 6.2. Finally I found it is the problem of Bars.HasNamedDataSeries. Here is the situation:

1) Just like before, I import my own ASCII stock data, in which I have three extra fields for each bar (fields "XXX", "YYY", "ZZZ"). And I import the ASCII stock data into WL successfully.

2) I can run strategies against one single stock or a group of stocks without problems.

3) But I have problems with "single symbol simulation" (like RSI Rotation). You know, I just need to click one symbol in the group to run the simulation. However, only the symbol I clicked return true for Bars.HasNamedDataSeries, and all other symbols return false. Therefore, I cannot get data for fields "XXX", "YYY", and "ZZZ". Any thoughts?
profile picture

Eugene

#2
Unfortunately, there's a number of known bugs in Named DataSeries. For the complete list please refer to the Open Issues page in the Wiki:

Open Issues > Named DataSeries bugs
profile picture

wbzhang

#3
can I switch back to WL 6.1, could you provide me download for that? At least it is functional in WL 6.1. thanks..
profile picture

Shourui

#4
I got the problem too. Can we go back to 6.1 version? We need to run the strategy every day!
profile picture

Eugene

#5
Shourui, please contact Fidelity. Wenbin, please enter a ticket and we'll arrange that.
profile picture

Cone

#6
@Shourui - Fidelity support can help you with a download for 6.1 since 6.2 was not a mandatory upgrade for WLP.

wbzhang - Please create a support ticket for a temporary download link.

In both cases, to downgrade, uninstall 6.2 via Add/Remove programs and then install 6.1.
profile picture

wbzhang

#7
Yes, I just created a support ticket. Let me know if you haven't received it.
profile picture

Shourui

#8
Hi, Eugene & Cone

I called Fidelity. the phone support guy called "wealthlab developer" and he said the developer's answer is "NO WAY to go back to 6.1". This is totally unacceptable. I don't believe the "developer" is corret. Are you going to arrage reinstalling 6.1 with wbzhang? Can you give me some details so that Fidelity guys can know how to do it?

THX!
profile picture

Cone

#9
Whoever you spoke to must be confused. It's just a matter of providing a link to a 6.1 installation. 6.1 was a mandatory upgrade, but 6.2 was not. They can do this. Ask to talk to someone else.
profile picture

Sammy_G

#10
Shourui, other methods of getting the file:
- check your backups to see if you already have the file; its named "WealthLabProSetup" and will be dated around mid-January 2011, size approx 13.3 MB
- if you have Windows Vista or Windows 7, right-click the current "WealthLabProSetup" file (which is now v6.2) located in "C:\Users\[user name]\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0" and choose 'Restore previous versions'; Windows will search the Restore Points for previous versions; look for one dated around mid-January 2011, size around 13.3 MB
- if all else fails, give me your email address and I will email you my copy of the file (its the 32-bit version, date/size as noted above); I just hope I can send a 13.3 MB file as an attachment!
profile picture

Cone

#11
Good call Sammy_G. You can reinstall via the MSI cached file. Uninstall 6.2, then double click the MSI cached installation. You can find it...

in XP:
C:\Documents and Settings\[user who installed]\Local Settings\ApplicationData\Downloaded Installations

in Vista/7
C:\Users\[user who installed]\AppData\Local\Downloaded Installations\

then, for the 32-bit intallation:
\{AB88AABE-57F0-4FEC-A6D0-D31A2D8D75C9}\Wealth-Lab Pro 6.1.msi

for the 64-bit intallation:
\{A8490A7A-9D47-41E0-A0D6-F7827208EAA9}\Wealth-Lab Pro 6.1 (64-bit).msi

If you don't find those directory GUIDs, it's possible I'm wrong about those. If so, just click through them until find the 6.1.msi file.
profile picture

Shourui

#12
Sammy_G,
Thanks for your advice! I found Wealth-Lab Pro 6.1.msi in the folder mentioned by Cone.

Corn,
If I uninstall 6.2 and reinstall 6.1, do I still have current strategies, workspaces, datasets and watchlists after 6.1 installation?

Thank you, guys.



profile picture

Eugene

#13
Yes you will still have them.

p.s. If you haven't updated the visualizer extensions yet, don't do it.
profile picture

Shourui

#14
Hi, Eugene

I uninstalled 6.2 and install 6.1. I got FindnamedSeries working, but SetContext("SYMBOL_TEST",true) is still not working correctly. It only works on any original ASCII dataset or watchlists which contain symbol from the dataset which has "SYMBOL_TEST". If the watchlist doesn't have any symbol from the dataset having "SYMBOL_TEST", it will throw out the runtiem error: could not fin symbol "SYMBOL_TEST".
Is there any way to reinstall old version of Aronow Software LLC wathcilist Static Data Provider? I believe the version associated with 6.1 in Jan 2011 should work. The newest one v.2.1.0.0 was released on 2/13/2011.

(copied from another thread in question cateogry "WealthScript (.NET)" )
profile picture

Eugene

#15
No, we do not plan for extension downgrades. In addition, the old version doesn't work with 64-bit WL5/6.
profile picture

Shourui

#16
My computer is 32bit. Is there a link I can use to download the old version? How long will it take to get the bug fixed?

update: I found file "AronowSoftware.DataProviders.Watchlist_1.0.0.0.wle" dated on 9/13/2010 in my computer. If I uninstall the current version 2.0.0.0 and install the extension 1.0.0.0. would I experience any trouble and the current watchlists still exist? Please help. I want to make sure there would be no mess, before I take any action on this. Thanks.
profile picture

Eugene

#17
This is a 3rd party extension. To avoid mess, in this thread let's concentrate on Bars.NamedDataSeries problems in WL 6.2, please. Thanks.
profile picture

Eugene

#18
One more (4th) Named DataSeries bug added to the Open Issues list:

Wiki > Named DataSeries bugs

Actually, it's been there since 6.0.
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).