If a stock symbol name contains a slash, some of the Fidelity provided fundamentals (i.e. estimated earnings) cannot be accessed. See attachment.

In addition, orders cannot be placed by the WL Orders window if a symbol name contains a slash. The work around there is to remove the slash, then try placing the order again. (Or don't use WL to place the order in the first place.)

I heard that Fidelity used two different symbology sets. Have you tried BRK.B and BF.B?

QUOTE:
Have you tried BRK.B and BF.B?

No I haven't tried replacing the slash "/" with a period. I get all my leads from the Fidelity stock screener, which employs the slash instead of the period. Thanks for the tip.

Well, when the symbol employs a period instead of a slash, this approach works some of the time with the Fidelity earnings estimate provider. Notice from the screenshot, the BRK.B symbol is recognized but not the BF.B symbol.

But the real problem is the Chart window says "No Data Available" for both symbols with the period. So my new question is what punctuation must be used so both the Chart window and the Fidelity earnings estimate provider can recognize these symbols with punctuation? I want to employ punctuation that works for all Fidelity providers.

It turns out that Fidelity A/B shares symbology not matching that of GICS is a long standing bug.

If one strips out all punctuation from symbols BF.B and BRK.B, everything works for BFB, but the static estimated earnings data still won't download for BRKB, see attachment below. It would be nice if BRKB for estimated earnings worked too. At any rate, the best compromising work around is to strip out all punctuation until this punctuation issue is properly fixed in WL.

QUOTE:
... Fidelity A/B shares symbology not matching that of GICS is a long standing bug.

Any idea when that will be fixed?

Forgot the attachment.

Glad you've found the workaround. That's right, BRK.B VIA.B become BRKB VIAB and so on.

QUOTE:
Any idea when that will be fixed?

Sorry, no ETA for this one yet. Some higher priority bugs are in the focus.