NoNestedPartySubIDs (FIX tag 804)

NumInGroupFIX 4.4FIX 5.0 SP2group counter

NoNestedPartySubIDs (tag 804) is a NumInGroup field defined in FIX 4.4 and FIX 5.0 SP2. It appears in 22 message types, always optionally. 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
804
Name
NoNestedPartySubIDs
Datatype
NumInGroup (int)
Dialects
FIX 4.4 and FIX 5.0 SP2
Messages
22

What the specification says

Number of NestedPartySubID (545) and NestedPartySubIDType (805) entries

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

A real message using tag 804

ExecutionReport · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength199
35MsgType8Execution Report
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
37OrderIDORD-10042
17ExecIDEXEC-88117
150ExecType0New
39OrdStatus0New
54Side1Buy
151LeavesQty0
14CumQty1000000
6AvgPx1.09215
555NoLegs1 entry1repeating group
600LegSymbolEXAMPLE
539NoNestedPartyIDs1 entry1repeating group
524NestedPartyIDEXAMPLE
804NoNestedPartySubIDs2 entries2repeating group
545NestedPartySubIDEXAMPLE
545NestedPartySubIDEXAMPLE
10CheckSum228
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 804 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 5.0 SP2Where in the message
AdjustedPositionReportBLOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
AllocationInstructionJOptionalOptionalinside AllocGrp › NestedParties › NstdPtysSubGrp
AllocationInstructionAckPOptionalinside AllocAckGrp › NestedParties › NstdPtysSubGrp
AllocationInstructionAlertBMOptionalinside AllocGrp › NestedParties › NstdPtysSubGrp
AllocationReportASOptionalOptionalinside AllocGrp › NestedParties › NstdPtysSubGrp
AllocationReportAckATOptionalinside AllocAckGrp › NestedParties › NstdPtysSubGrp
ApplicationMessageRequestBWOptionalinside ApplIDRequestGrp › NestedParties › NstdPtysSubGrp
ApplicationMessageRequestAckBXOptionalinside ApplIDRequestAckGrp › NestedParties › NstdPtysSubGrp
AssignmentReportAWOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
CrossOrderCancelReplaceRequesttOptionalOptionalinside SideCrossOrdModGrp › PreAllocGrp › NestedParties › NstdPtysSubGrp
ExecutionReport8OptionalOptionalinside InstrmtLegExecGrp › NestedParties › NstdPtysSubGrp
MultilegOrderCancelReplaceACOptionalOptionalinside LegOrdGrp › NestedParties › NstdPtysSubGrp
NewOrderCrosssOptionalOptionalinside SideCrossOrdModGrp › PreAllocGrp › NestedParties › NstdPtysSubGrp
NewOrderListEOptionalOptionalinside ListOrdGrp › PreAllocGrp › NestedParties › NstdPtysSubGrp
NewOrderMultilegABOptionalOptionalinside LegOrdGrp › NestedParties › NstdPtysSubGrp
NewOrderSingleDOptionalOptionalinside PreAllocGrp › NestedParties › NstdPtysSubGrp
OrderCancelReplaceRequestGOptionalOptionalinside PreAllocGrp › NestedParties › NstdPtysSubGrp
PositionMaintenanceReportAMOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
PositionMaintenanceRequestALOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
PositionReportAPOptionalOptionalinside PositionQty › NestedParties › NstdPtysSubGrp
QuoteSOptionalOptionalinside LegQuotGrp › NestedParties › NstdPtysSubGrp
QuoteRequestROptionalOptionalinside QuotReqGrp › QuotReqLegsGrp › NestedParties › NstdPtysSubGrp
QuoteRequestRejectAGOptionalOptionalinside QuotReqRjctGrp › QuotReqLegsGrp › NestedParties › NstdPtysSubGrp
QuoteResponseAJOptionalOptionalinside LegQuotGrp › NestedParties › NstdPtysSubGrp
QuoteStatusReportAIOptionalOptionalinside LegQuotStatGrp › NestedParties › NstdPtysSubGrp
RegistrationInstructionsoOptionalOptionalinside RgstDtlsGrp › NestedParties › NstdPtysSubGrp
TradeCaptureReportAEOptionalOptionalinside TrdInstrmtLegGrp › NestedParties › NstdPtysSubGrp
TradeCaptureReportAckAROptionalOptionalinside TrdInstrmtLegGrp › NestedParties › NstdPtysSubGrp

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 804 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);// NoNestedPartySubIDs is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[804] is undefined.const entries = message.groups[804] ?? [];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