CustDirectedOrder (FIX tag 1029)
CustDirectedOrder (tag 1029) is a Boolean field defined in FIX 5.0 SP2. It appears in 3 message types, always optionally.
At a glance
- Tag
- 1029
- Name
- CustDirectedOrder
- Datatype
- Boolean (char)
- Dialects
- FIX 5.0 SP2
- Messages
- 3
What the specification says
Indicates if the customer directed this order to a specific execution venue "Y" or not "N".
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1029
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 118 | |
| 35 | MsgType | D | NewOrderSingle |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 11 | ClOrdID | ORD-10042 | |
| 54 | Side | 1 | Buy |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 1029 | CustDirectedOrder | N | |
| 10 | CheckSum | 157 |
Shown with | separators for readability. On the wire FIX uses SOH (0x01), an invisible control byte — and because BodyLength and CheckSum are computed over the actual bytes, the two forms have different checksums. Both are valid and both decode here.
Generated from the FIX 5.0 SP2 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Where tag 1029 appears
Requiredness is a property of the message, not of the field: the same tag can be optional in one message and conditionally required in another.
| Message | MsgType | Requiredness | Where in the message |
|---|---|---|---|
| ExecutionReport | 8 | Optional | directly on the message body |
| NewOrderSingle | D | Optional | directly on the message body |
| OrderCancelReplaceRequest | G | Optional | directly on the message body |
Wire format
Y or N. Not 1/0, and not true/false. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.
Read tag 1029 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const field = message.fields[1029];field?.name; // "CustDirectedOrder"field?.raw; // the verbatim wire stringfield?.value; // coerced to a booleanOther Boolean fields
- 1028ManualOrderIndicator
- 1057AggressorIndicator
- 978LateIndicator
- 1091PreTradeAnonymity
- 1134ReportedPxDiff
- 912LastRptRequested
- 893LastFragment
- 1171PrivateQuote
- 1187RefreshIndicator
- 852PublishTrdIndicator
- 1242FlexProductEligibilityIndicator
- 1243DerivFlexProductEligibilityIndicator
- 1244FlexibleIndicator
- 797CopyMsgIndicator
- 754AutoAcceptIndicator
- 720PriorSpreadIndicator
- 719ContraryInstructionIndicator
- 1352ApplResendFlag
- 700ReversalIndicator
- 1389TrdRepIndicator
- 650LegalConfirm
- 1410DefaultVerIndicator
- 636WorkingIndicator
- 575OddLot
Decode this in your own code
The same engine that produced the decoded example above is an Apache-2.0 npm package with zero runtime dependencies. It runs in Node and in the browser, and parse() returns problems as data instead of throwing.
npm i @boarteam/fix @boarteam/fix-dict-fix50sp2