NoPartySubIDs (FIX tag 802)

NumInGroupFIX 4.4group counter

NoPartySubIDs (tag 802) is a NumInGroup field defined in FIX 4.4. It appears in 44 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: 802
Name: NoPartySubIDs
Datatype: NumInGroup (int)
Dialects: FIX 4.4
Messages: 44

What the specification says

Number of PartySubID (523)and PartySubIDType (803) entries

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

A real message using tag 802

ExecutionReport · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	181
35	MsgType	8	Execution Report
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
37	OrderID	ORD-10042
453	NoPartyIDs1 entry	1	repeating group
448	PartyID	EXAMPLE
802	NoPartySubIDs2 entries	2	repeating group
523	PartySubID	EXAMPLE
523	PartySubID	EXAMPLE
17	ExecID	EXEC-88117
150	ExecType	0	New
39	OrdStatus	0	New
54	Side	1	Buy
151	LeavesQty	0
14	CumQty	1000000
6	AvgPx	1.09215
10	CheckSum	227

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 802 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
AllocationInstruction	J	Optional	inside Parties › PtysSubGrp
AllocationInstructionAck	P	Optional	inside Parties › PtysSubGrp
AllocationReport	AS	Optional	inside Parties › PtysSubGrp
AllocationReportAck	AT	Optional	inside Parties › PtysSubGrp
AssignmentReport	AW	Optional	inside Parties › PtysSubGrp
CollateralAssignment	AY	Optional	inside Parties › PtysSubGrp
CollateralInquiry	BB	Optional	inside Parties › PtysSubGrp
CollateralInquiryAck	BG	Optional	inside Parties › PtysSubGrp
CollateralReport	BA	Optional	inside Parties › PtysSubGrp
CollateralRequest	AX	Optional	inside Parties › PtysSubGrp
CollateralResponse	AZ	Optional	inside Parties › PtysSubGrp
Confirmation	AK	Optional	inside Parties › PtysSubGrp
CrossOrderCancelReplaceRequest	t	Optional	inside SideCrossOrdModGrp › Parties › PtysSubGrp
CrossOrderCancelRequest	u	Optional	inside SideCrossOrdCxlGrp › Parties › PtysSubGrp
ExecutionReport	8	Optional	inside Parties › PtysSubGrp
MassQuote	i	Optional	inside Parties › PtysSubGrp
MassQuoteAcknowledgement	b	Optional	inside Parties › PtysSubGrp
MultilegOrderCancelReplace	AC	Optional	inside Parties › PtysSubGrp
NewOrderCross	s	Optional	inside SideCrossOrdModGrp › Parties › PtysSubGrp
NewOrderList	E	Optional	inside ListOrdGrp › Parties › PtysSubGrp
NewOrderMultileg	AB	Optional	inside Parties › PtysSubGrp
NewOrderSingle	D	Optional	inside Parties › PtysSubGrp
OrderCancelReplaceRequest	G	Optional	inside Parties › PtysSubGrp
OrderCancelRequest	F	Optional	inside Parties › PtysSubGrp
OrderMassStatusRequest	AF	Optional	inside Parties › PtysSubGrp
OrderStatusRequest	H	Optional	inside Parties › PtysSubGrp
PositionMaintenanceReport	AM	Optional	inside Parties › PtysSubGrp
PositionMaintenanceRequest	AL	Optional	inside Parties › PtysSubGrp
PositionReport	AP	Optional	inside Parties › PtysSubGrp
Quote	S	Optional	inside Parties › PtysSubGrp
QuoteCancel	Z	Optional	inside Parties › PtysSubGrp
QuoteRequest	R	Optional	inside QuotReqGrp › Parties › PtysSubGrp
QuoteRequestReject	AG	Optional	inside QuotReqRjctGrp › Parties › PtysSubGrp
QuoteResponse	AJ	Optional	inside Parties › PtysSubGrp
QuoteStatusReport	AI	Optional	inside Parties › PtysSubGrp
QuoteStatusRequest	a	Optional	inside Parties › PtysSubGrp
RegistrationInstructions	o	Optional	inside Parties › PtysSubGrp
RegistrationInstructionsResponse	p	Optional	inside Parties › PtysSubGrp
RequestForPositions	AN	Optional	inside Parties › PtysSubGrp
RequestForPositionsAck	AO	Optional	inside Parties › PtysSubGrp
SettlementInstructionRequest	AV	Optional	inside Parties › PtysSubGrp
SettlementInstructions	T	Optional	inside SettlInstGrp › Parties › PtysSubGrp
TradeCaptureReport	AE	Optional	inside TrdCapRptSideGrp › Parties › PtysSubGrp
TradeCaptureReportRequest	AD	Optional	inside Parties › PtysSubGrp

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 802 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);// NoPartySubIDs is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[802] is undefined.const entries = message.groups[802] ?? [];for (const entry of entries) {  // entry.fields is keyed by tag; entry.groups holds nested groups}

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

Try the decoder Source on GitHub