Clarification on Entering Stop Orders via ExecutionUpdate / OrderUpdate

[reach4thelasers]

Hey there.

I've got unexpected behavior related to Market orders on the Unmanaged Order API. I was previously holding a reference to the order object and checking for OrderUpdate or ExecutionUpdate. This no longer works for market orders and I note that the docs have been updated and now say:

- If you are relying on the OnExecutionUpdate() method to trigger actions such as the submission of a stop loss order when your entry order is filled, ALWAYS reference the properties on the Order object property attached to the Execution object passed into the OnExecutionUpdate() method.

- If you are relying on the OnOrderUpdate() method to trigger actions such as the submission of a stop loss order when your entry order is filled ALWAYS reference the properties on the Order object passed into the OnOrderUpdate() method.

To say the least this is vague. "Always reference the properties on the Order Object"

Which properties?? Furthermore, all the examples provided for this do not adhere to these new rules. Are these going to be updated?

The only Properties I can use at the moment are OCO ID and SignalID - neither of which are intended to be used for Uniquely identifying an order; The signal field doesn't even enforce uniqueness and is intended to be a human readable description, not an Identifier.

What is the recommended approach to uniquely identifying an order?

[NinjaTrader_AlanP]

Hello reach4thelasers,

The properties on an order Object are listed at the following link under Methods and Properties, for example LimitPrice or Name.

https://ninjatrader.com/support/helpGuides/nt8/en-us/?order.htm

An example of a recommended approach to uniquely identifying an order would be the following from within OnOrderUpdate,

if (order.Name == "myEntryOrder")
      entryOrder = order;

Where order.Name would refer to the signal name of the entry order.

If you had suggestions for how the helpguide could be improved, or could cite the examples you mention don't abide by the rules, that would be helpful. Or if you'd like to sample of the code you're having issues with, please do so.

Please let us know if need further assistance.

[GeoOrtiz]

Hi All,

Following this theme, how would you reference the entry order if you setup bracket orders as your entry orders? One of the bracket orders will be filled and the other order will be cancelled (OCO orders). When you write your:

if (order.Name == "myEntryOrder")
entryOrder = order;

statement, how does the system know that "order" is the filled order and not the cancelled order? Or is there another way to handle OCO orders in the OnOrderUpdate / OnExecutionUpdate methods?

All help is appreciated!

[NinjaTrader_AlanP]

Hello GeoOrtiz,

The following if statement will check that both the name = myEntryOrder and that the state of that order is in OrderState.Filled.

if(order.Name =="myEntryOrder"  && order.OrderState == OrderState.Filled)

Please let us know if you need further assistance.

[GeoOrtiz]

Thank you Alan! That did the trick!