+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-1377

Can't select "NI225_M" when I create a custom futures(eSignal)

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

I create "NI225_M" root in eSignal Symbol Dictionary.
But when I create a custom futures, "NI225_M" doesn't appear in symbol root.
Please see attached screen shorts.
"NI225_M" has under-bar("_"). I guess this is because of the under-bar.
Please help me.
*NI225_M is a symbol root of Nikkei 225 Index Mini Futures
*Quote Manager version is 8.5.6851.400

Steps to reproduce this issue

How to reproduce
1. Create "NI225_M" root in eSignal Symbol Dictionary.
2. Select Symbol Root in "Edit Custom Futures" window.
"NI225_M" doesn't appear.

Comments (2)
user-offline.png  ducktail (ducktail)
Sep 16, 2014 - 11:11

I have changed the main data feed from IB to eSignal recentry because of data accuracy.
So I really want you to fix this problem. Please help.
I found related topic.

But when I made this workarround, I couldn't get realtime data.

user-offline.png  MultiCharts Support (MultiCharts)
May 20, 2015 - 22:27

It is not possible to use the "" sign in Symbol Root when creating a Custom Futures by design.
It comes because such symbols are used in the formula to create custom futures from individual contracts.
1. Change the symbol root sign from the " _" to the "-".
2. Add several individual contracts.
3. Select all the contracts -> right click on them -> Edit Symbols.
4. Change the Symbol Root sign from the "
" to the "-" for all of them.
When adding next contracts, please make sure that you changed that.

Issue basics
User pain
  • Type of bug
    Not triaged
  • Likelihood
    Not triaged
  • Effect
    Not triaged
Affected by this issue (2)
People involved
Times and dates
  • Posted at
  • Last updated
Issue details
  • Resolution
    Not determined
  • Severity
Attachments (2)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates