I have created lists for rus1000, sp500, sp400, sp600, nas100, etc, using the Data Manager. Also created lists for major sectors ( like Healthcare, InfoTech, BioTech, Energy ), using Fidelity screener, then reduced these lists to close > 5, vol > 250k.
I would now like to see which index list the various sector tickers are in if any. Is there an easy way to do this in WL?

Thanks for any help, Bill

The code example for Community.Components' Input function does just that: type in one or several symbols, and the code will list the DataSet(s) the symbol is in:

Input

I think Eugene gave you what you were asking for, but since you said "sector tickers"...

CODE:
Please log in to see this code.

For this to work, make sure that you update Industry Data for the Fidelity Provider.

More in the WealthScript Programming Guide: Fundamental Analysis > GICS Data

Cone, Eugene, thanks for the reply!

I have updated the Fidelity Sector , Industry data and would like to run a strategy on my lists and see the symbol and sector / group info results. Then export to excel.

Cone, I'm not sure how to get the strategy to do that? Looking at the "More in the WealthScript Programming Guide: Fundamental Analysis > GICS Data" example, how do I modify the strategy.

Thanks for any help

Cone, ok trying to figure this out myself? I think there were two small errors in the code you posted above?

Bar.Symbol should be Bars.Symbol? and Gics.Desc should be Gics.GetDesc?

Anyway when I compile that its ok and when run I get the message,

"The given key was not present in the dictionary."

Bill

Sorry about the errors... corrected for future views.

Re: "The given key was not present in the dictionary."
Occurs when the Gics data isn't present for the symbol. You should use a try/catch block like the example in the Programming Guide to work around this condition. Which symbol is failing?

Cone;
I'm not very good with code, here is what I ran on the sp500 list, getting the "The given key was not present in the dictionary." message

CODE:
Please log in to see this code.

If you use ClearDebug in the code and run it on a DataSet, you'll only see the result for the last symbol. What are you trying to accomplish?

If you want to see which symbols are failing, clear the debug window manually and run the code below. Two symbols that shouldn't fail, but do are BFB and BRKB. The problem is the different types of symbology used at Fidelity. For Gics, these symbols will be found as BF.B and BRK.B, so you can do a code substitution as shown.

CODE:
Please log in to see this code.

Cone; you asked? What are you trying to accomplish?

I am trying to run a strategy on a given list ( say sp500 ), click on "symbol" tab and see the sector / industry each ticker is in.
Then export to excel for "mix and match"

I ran the code above and the debug shows " key not present " for all symbols! I go to Data Manager, create new list, select Fidelity, select "Select the Symbols from predefined Industry Classification groups, select update industry Data, promt log-in to Fidelity, log in, update industry groups, "hourglass" maybe 10 seconds and then appears to be done?????

Note; when I get the Industry Classification / Update Industry Data View, there are no sectors / groups in the left view to move to the right "selected" view???? Seams to me the Sector / Groups were once there???

It sounds like you've downloaded the data correctly. Do you see the Gics.xml file in the C:\Users\[You]\AppData\Roaming\Fidelity Investments\WealthLabPro\1.0.0.0\Data folder ? If so, is it about 76KB?

Cone, I found the file but it is empty???

Note; when I go to Data Manager, create new list, select Fidelity, select "Select the Symbols from predefined Industry Classification groups,get the Industry Classification / Update Industry Data View, there are no sectors / groups in the left view to move to the right "selected" view???? Seams to me the Sector / Groups were once there???

Should I call Fidelity TS or do you have other suggestions??/

Cone and Eugene,

I just talked with Adam at Fidelity Tech Support and this is a "Know Problem" at Fidelity and they hope to have a fix soon! F.Y.I.

Thanks for your help as always, Bill

Thanks for the information, Bill.