MultiCharts Easter Sale has jumped in! Up to 50% off Explore offers
+1 888 340 6572
MultiCharts Project Management
previous_open_issue.png
Go to the previous open issue
previous_issue.png
Go to the previous issue (open or closed)
star_faded.png
Please log in to bookmark issues
feature_request_small.png
Open Feature request MC-1764

QM Custom futures can not select symbol root "NI225_M" esignal data source.

action_vote_minus_faded.png
0
Votes
action_vote_plus_faded.png
next_issue.png
Go to the next issue (open or closed)
next_open_issue.png
Go to the next open issue
Description

Version 9.0 Release (Build 10014)
QM Custom futures can not select symbol root "NI225_M" esignal data source.
There is 2 symbol in symbol dictionary "NI225" and "NI225_M".
Only could select "NI225" custom futures symbol root drop down menu.

Steps to reproduce this issue

Same as above.

Comments (3)
#0
user-offline.png  MultiCharts Support (MultiCharts)
Oct 13, 2014 - 14:51

At the moment roots with underscore symbol "_" are not supported.

#0
user-offline.png  MultiCharts Support (MultiCharts)
Oct 13, 2014 - 14:54

As a workaround you can use a symbol root that is supported and define it to all required symbols (even if their names do not include this supported root name).

#0
user-offline.png  MultiCharts Support (MultiCharts)
May 20, 2015 - 18:26

The explanation and the workaround can be found here:
http://www.multicharts.com/pm/viewissue.php?issue_no=MC-1377

History
Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
  • Posted by
    user-offline.png  YK (YK)
  • Owned by
    Not owned by anyone
  • Assigned to
    Not assigned to anyone
  • Subscribers
    1 subscriber(s)
    Click here to show the list of subscribers
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
    Critical
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