Login Page - Create Account

Support Board


Date/Time: Sat, 10 May 2025 15:51:57 +0000



[User Discussion] - ACSIL One Time Processing per Order

View Count: 802

[2016-02-15 18:30:39]
rhovega - Posts: 279
Could provide an example of One Time Processing per OrderID to add to your documentation. Have found nothing similar in either your online documentation nor on the provided cpp code templates.

I used the order modification example provided within tradesystem.cpp combined with sc.GetNearestTargetOrder/sc.GetNearestStopOrder and PositionData.AveragePrice to create a study that modifies attached orders of manually executed orders to a value determine by ATR.

It works fine, but the code uptades attached orders continuously and overrides attached orders manual modification. The solution to these two unwanted conditions would be to get the code to run only once per OrderID.

Could you help with this?

Thank you.
Date Time Of Last Edit: 2016-02-15 19:03:35
[2016-02-15 19:24:04]
Sierra Chart Engineering - Posts: 104368
This is not within the scope of our support.
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
[2016-02-15 22:11:31]
rhovega - Posts: 279
OK

For those looking into something similar, found a roundabout to achieve the same objective: order modification only runs when "PositionData.LastEntryDateTime == sc.LatestDateTimeForLastBar".

To post a message in this thread, you need to log in with your Sierra Chart account:

Login

Login Page - Create Account