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

Get the underlying symbol Name for a Custom symbol

action_vote_minus_faded.png
2
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

hi,
Its there a way for me in powerlanguage to get the actual symbol name of a custom continuous symbol ?
E.g Say i name my custom symbol as "NK near", but the actual underlying symbol is now "NK M2".
If i apply an indicator on "NK near" is there a keyword/function i can call to get "NK M2" ?
thanks
Related to forum post http://www.multicharts.com/discussion/viewtopic.php?f=1&t=10466

Steps to reproduce this issue
Comments (1)
#0
user-offline.png  mc-528 (MC_528)
Aug 16, 2012 - 22:28

yes, please can there be a Keyword added called: underlying_symbolname for use when charting a Custom Futures Instrument?
To use another example, for Interactive Broker's Datafeed,  if your Custom Symbol was called ES#, then calling the proposed keyword   underlying_symbolname  on a chart bar dated
1 Aug 2010  would return the  underlying symbol name  ESU0,  whereas calling it on a bar dated
1 Aug 2012 would return the true underlying symbol name ESU2
Every bar on a Custom Futures chart would have to know, what it's true underlying source of data is.
Thanks for considering.

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