Limit Order Keeping Alive or Resubmitting

[durdcash]

Hello,

I have been working on using the enterlonglimit and entershortlimit code from using code snippets from other posts and the resource library. I have enacted the keep order alive until cancelled because I have seen that has been easier for me. I have been trying to find out how to properly add my cancel conditions but I am not sure the best course of action. I know the resource library says to add on orderupdate but when I tried that I seemed to have issues. Is there a way to keep it on bar update and change how its coded? Or is it better to switch this to resubmit the order until my other conditions are no longer true? Should the logic be added in the same if bracket { logic here} on bar update or do I create its own somewhere else?

I am unable to share the actual code because I had someone work on it last year. It is a managed approach but then internally there is also a lot of conditional order placement codes built in (not sure if that's the proper terminology). Is there a way for me to add those conditional order placement ideas without explicitly using a limit order then? If so, I could create the bool values and then it would submit the market order when it reaches my proper pullback that I wanted.

Once all my order conditions are true currently I will place a limit order at the Low[2] or high[2]. All of this is working properly but what I want to have happen is to cancel the order if Close[0]>=Profit Traget1 or Bars since signal is >= user defined # or time is after my specified close.

There used to be an old piece of code I found but cannot find anymore that I believe would have been able to answer my questions but I cannot find it on the forum anywhere at this popint

Any help pointing me into the right direction is appreciated!

[NinjaTrader_ChelseaB]

Hello durdcash,

There is an example of trailing / chasing logic that would have all of this in it: assigning orders to variables in OnOrderUpdate(), cancelling orders, keeping Exit orders alive with isLiveUntilCancelled as true, etc.

https://ninjatrader.com/support/forum/forum/ninjatrader-8/platform-technical-support-aa/97419-priceos-cs-expecting?p=802269#post802269

[durdcash]

NinjaTrader_ChelseaB thanks for providing that but I am not sure if that's what I was looking for at first glance.I will take a look at them in more detail later today and see if they are able to provide the proper insight

[durdcash]

NinjaTrader_ChelseaB I have dug a little deeper and might be able to switch up some of the logic and rework it for my strategy. Would I need private void AssignOrderToVariable, OnOrderUpdate, and OnExecutionUpdate for this to function properly or can any of these be done without when I go and code it to test? Essentially so I could make sure one piece is working before I move to the next piece?

[NinjaTrader_ChelseaB]

Hello durdcash,

The AssignOrderToVariable() assigns the order object from OnOrderUpdate() to a variable, so that the order can be modified in OnBarUpdate().
This is called from OnOrderUpdate(). You do not have to have a separate method for this, but if you want to modify an existing order with ChangeOrder() assigning the order to a variable would be necessary.
OnExecutionUpdate() is where the stop is first being submitted when the entry order fills. If you do not want to submit the stop when the entry order fills, then this override would not be necessary.

[durdcash]

NinjaTrader_ChelseaB thank you for the clarification. Now if I want to cancel the order after a number of bars are passed, will I want to use on order update or can that also be done on bar update if done properly? I do not use the set method and use internal on bar update code to trigger my stops, targets, and what not.

[NinjaTrader_ChelseaB]

Hello durdcash,

To cancel an order, you will need to assign the order object to a variable in OnOrderUpdate(), then supply the variable holding that order to CancelOrder() in OnBarUpdate().

https://ninjatrader.com/support/helpGuides/nt8/managed_cancelorder.htm