Add ExecutionId to OrderEvent and SerializedOrderEvent #9250
+24
−1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Add
ExecutionIdproperty toOrderEventandSerializedOrderEventclasses to store the unique execution identifier provided by brokerages.Changes:
ExecutionIdproperty toOrderEvent(ProtoMember 20, JsonProperty with DefaultValueHandling.Ignore)ExecutionIdproperty toSerializedOrderEventwith backward compatibility setter forexecution-idFromSerializedmethod to map ExecutionIdSerializedOrderEventconstructor to copy ExecutionId from OrderEventRelated Issue
Closes #9133
Motivation and Context
Algorithms that maintain virtual position trackers (e.g., for pairs trading, multi-leg strategies) need unique execution identifiers to keep positions in sync with the brokerage. This enables deduplication and reconciliation logic in user algorithms.
Requires Documentation Change
No documentation changes required. This is an optional field that brokerages can populate.
How Has This Been Tested?
Types of changes
Checklist:
bug-<issue#>-<description>orfeature-<issue#>-<description>