Support Board
Date/Time: Mon, 13 Jan 2025 18:32:24 +0000
Intelligent stop management possible?
View Count: 631
[2017-04-29 04:58:48] |
tobi - Posts: 351 |
Is it possible to achive the following within the DOM / target and stop management? - Attached orders (10 points stop and 10 points target) checked - Long entries (e.g): 1st position entry at 10.050 (=> stop at 10.040, target at 10.060) 2nd position entry at 10.048 (=> stop at 10.038, target at 10.058) -> I manually change the target to 10.056; stop stays at 10.038 3rd position entry at 10.053 (=> stop at 10.043, target at 10.063) -> I manually change the target to 10.054; stop stays at 10.043 - Target of the 3rd position (10.054) gets hit => Not the stop of this position (10.043) should be deleted but the stop furthest away (10.038) ... and so on In other words, is it possible that when working with several individual entries (with attached orders) and the position is being reduced (target/limit reached or manually reduced by market order), that the stop furthest away will be delete and not the stop related to the attached order that is just being closed? Is there any way to achive this? Date Time Of Last Edit: 2017-04-29 11:26:42
|
[2017-04-30 18:12:33] |
Sierra Chart Engineering - Posts: 104368 |
Target of the 3rd position (10.054) gets hit => Not the stop of this position (10.043) should be deleted but the stop furthest away (10.038) or manually reduced by market order), that the stop furthest away will be delete and not the stop related to the attached order that is just being closed?
Yes this can be done. Refer to:Attached Orders: Scaling Out Sierra Chart Support - Engineering Level Your definitive source for support. Other responses are from users. Try to keep your questions brief and to the point. Be aware of support policy: https://www.sierrachart.com/index.php?l=PostingInformation.php#GeneralInformation For the most reliable, advanced, and zero cost futures order routing, *change* to the Teton service: Sierra Chart Teton Futures Order Routing |
To post a message in this thread, you need to log in with your Sierra Chart account: