+1 888 340 6572
MultiCharts Project Management
Go to the previous open issue
Go to the previous issue (open or closed)
Please log in to bookmark issues
Open Feature request MC-2266

QuoteManager: Allow to exclude TEST symbols from TradeStation

Go to the next issue (open or closed)
Go to the next open issue

IN MultiCharts .NET64 QuoteManager > Instrument > Add Symbol > From Data Source > TradeStation... > Stock tab it would be immensely helpful if there was a checkbox that noted:
Exclude TEST symbols.

When adding symbols, there is no way to sort against TEST symbols to avoid them. This is due the symbol syntax. For example:
Description: ECCC
Exchange: AMEX

Hence, the exclusion could look for symbols that end in:

and not present them at all in the selection list.

This will avoid overly tedious manual removal of test symbols both during the symbol addition process, and after symbols have been added. Also, this will improve customer satisfaction with MultiCharts.

Comments (1)
user-offline.png  penalvch (penalvch)
Jun 22, 2017 - 20:31

Please also include those symbols that don't have .TEST in the Symbol field, but are test symbols.

For example:
Symbol: CBO
Description: CBO (Test Symbol)
Exchange: AMEX

Symbol: ZTEST
Description: ZTEST
Exchange: ARCX

Symbol: NTEST
Description: NTEST TEST Symbol
Exchange: NYSE

Symbol: NTEST.E
Description: NTEST.E
Exchange: NYSE

Symbol: SQZST
Description: Nasdaq Test Security
Exchange: NASDAQ

Symbol: SDZST
Description: SuperMontage Test
Exchange: NASDAQ

Issue basics
  • Type of issue
    Feature request
  • Category
    Not determined
  • Targeted for
    Not determined
  • Status
    Under Review
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (0)
There are no items
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
Attachments (0)
There is nothing attached to this issue
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates