PublishTrdIndicator (FIX tag 852)
PublishTrdIndicator (tag 852) is a Boolean field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 1 message type, always optionally. It is an enumerated field with 2 defined values.
At a glance
- Tag
- 852
- Name
- PublishTrdIndicator
- Datatype
- Boolean (char)
- Dialects
- FIX 4.4 and FIX 5.0 SP2
- Messages
- 1
- Valid values
- 2
What the specification says
Indicates if a trade should be reported via a market reporting service.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 852
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIX.4.4 | |
| 9 | BodyLength | 171 | |
| 35 | MsgType | AE | Trade Capture Report |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 571 | TradeReportID | EXAMPLE | |
| 570 | PreviouslyReported | N | not reported to counterparty |
| 32 | LastQty | 1000000 | |
| 31 | LastPx | 1.09210 | |
| 75 | TradeDate | 20240101 | |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 552 | NoSides1 entry | 1 | repeating group |
| 54 | Side | 1 | Buy |
| 37 | OrderID | ORD-10042 | |
| 852 | PublishTrdIndicator | N | Do not report trade |
| 10 | CheckSum | 215 |
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 4.4 dictionary and verified at build time: it parses and validates with no issues. Open the decoder to try your own message.
Valid values
A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.
| Value | Meaning | Symbolic name |
|---|---|---|
| Y | Report trade | YES / REPORT_TRADE |
| N | Do not report trade | NO / DO_NOT_REPORT_TRADE |
Where tag 852 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 | FIX 4.4 | FIX 5.0 SP2 | Where in the message |
|---|---|---|---|---|
| TradeCaptureReport | AE | Optional | Optional | directly on the message body |
| TradeCaptureReportAck | AR | — | 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 852 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const publishTrdIndicator = message.fields[852]?.raw;// e.g. "Y" — Report trade// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(852) ?.enumValues?.find((e) => e.value === publishTrdIndicator) ?.description;Other Boolean fields
- 893LastFragment
- 797CopyMsgIndicator
- 912LastRptRequested
- 754AutoAcceptIndicator
- 978LateIndicator
- 720PriorSpreadIndicator
- 719ContraryInstructionIndicator
- 700ReversalIndicator
- 1028ManualOrderIndicator
- 1029CustDirectedOrder
- 650LegalConfirm
- 1057AggressorIndicator
- 636WorkingIndicator
- 1091PreTradeAnonymity
- 575OddLot
- 570PreviouslyReported
- 1134ReportedPxDiff
- 547MDImplicitDelete
- 1171PrivateQuote
- 1187RefreshIndicator
- 464TestMessageIndicator
- 1242FlexProductEligibilityIndicator
- 1243DerivFlexProductEligibilityIndicator
- 1244FlexibleIndicator
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-fix44