Nonsense OnOrderUpdate() vs OnExecutionUpdate

[Dan_D_Trader]

Hi everyone.

In the NinjaScript language reference, it is noted on both OnOrderUpdate() and OnExecutionUpdate that

Notes:

•	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.

Why?

OnOrderUpdate() will be executed first and returning all the information about OrderState under various executed state such as Filled, PartFilled and so forth, including price, quantity, orderId, time, etc.
So why bother with OnExecutionUpdate() ?

Thank you.

[NinjaTrader_PatrickH]

Hello Dan_D_Trader,

Thank you for your post.

You reference the Order object passed to the OnExecutionUpdate() method as that is the Order object that is updating. You need to know which Order object is executed before you submit protective orders.

An execution is not the same thing as an order update. Orders can update for various reasons and only in states of Filled or PartFilled would you see an execution. Allowing for access to an Order update and an Execution update separately allows developers greater flexibility.

There is internal strategy logic that is triggered after OnOrderUpdate() is called but before OnExecutionUpdate() that can adversely affect your strategy if you are relying on tracking fills within OnOrderUpdate().

Please let me know if you