NoRelatedSym (FIX tag 146)

NumInGroupFIX 4.4FIX 4.2group counter

NoRelatedSym (tag 146) is a NumInGroup field defined in FIX 4.4 and FIX 4.2. It appears in 8 message types and is required in 4 of them. Its datatype is NumInGroup, which makes it a repeating-group counter: its value is the number of entries that follow, not a quantity in its own right.

At a glance

Tag
146
Name
NoRelatedSym
Datatype
NumInGroup (int)
Dialects
FIX 4.4 and FIX 4.2
Messages
8

What the specification says

Specifies the number of repeating symbols specified.

Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.

A real message using tag 146

MarketDataRequest · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength125
35MsgTypeVMarket Data Request
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
262MDReqIDREQ-1
263SubscriptionRequestType0Snapshot
264MarketDepth1
267NoMDEntryTypes1 entry1repeating group
269MDEntryType0Bid
146NoRelatedSym2 entries2repeating group
55SymbolEUR/USD
55SymbolEUR/USD
10CheckSum187
Edit and decode it yourself

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.

Open in the full decoder →

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.

Where tag 146 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.

MessageMsgTypeFIX 4.4FIX 4.2Where in the message
DerivativeSecurityListAAOptionalinside the RelSymDerivSecGrp component
EmailCOptionalOptionalinside the InstrmtGrp component
MarketDataRequestVRequiredRequiredinside the InstrmtMDReqGrp component
NewsBOptionalOptionalinside the InstrmtGrp component
QuoteRequestRRequiredRequiredinside the QuotReqGrp component
QuoteRequestRejectAGRequiredinside the QuotReqRjctGrp component
RFQRequestAHRequiredinside the RFQReqGrp component
SecurityDefinitiondOptionaldirectly on the message body
SecurityDefinitionRequestcOptionaldirectly on the message body
SecurityListyOptionalinside the SecListGrp component

Wire format

The number of entries in the repeating group that follows. The next field on the wire is the group's delimiter tag. @boarteam/fix parses the value as a number and reports parse/invalid-int when it does not lex as one; the raw string is kept either way.

Read tag 146 in TypeScript

decode.tsts
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix44";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);// NoRelatedSym is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[146] is undefined.const entries = message.groups[146] ?? [];for (const entry of entries) {  // entry.fields is keyed by tag; entry.groups holds nested groups}

Other NumInGroup fields

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