+1 888 340 6572 Try free for 30 days
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-1571

Assign Market Position at Broker requires position name field

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

When assigning initial market position at broker there is no ability to name the open position and thus when using 'PosTradeEntryName' as part of the exit criteria the open position will never be closed by Multicharts as the open position is unnamed.

See thread for full story: http://www.multicharts.com/discussion/viewtopic.php?f=1&t=45939

Steps to reproduce this issue

ExampleCode:

if EntryCondition1 = true buy ("tradeName") next bar at market at market
if ExitCondition1 = true and PosTradeEntryName(0,0) = "tradeName" then sell next bar at market

ExampleScenario:

  1. EntryCondition1 is met and a long trade called 'tradeName' has been executed.
  2. Multicharts/PC/Server/DataCenter goes down.
  3. Restart Multicharts and Assign Initial Market Position at Broker

Because the exit code requires the currently open trade to be called "tradeName" and this cannot be set by using Assign Initial Market Position at Broker there is no way for the currently open position at the broker to be handled by Multicharts.

Comments (0)
History
Issue basics
  • Type of issue
    Feature request
  • Category
    Usability
  • Targeted for
    Not determined
  • Status
    Under Review
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
    Critical
Attachments (1)
Commits (0)
There are no code checkins for this issue
Duplicate issues (0)
This issue does not have any duplicates