NoAllocs (FIX tag 78)

NumInGroupFIX 4.4FIX 4.2FIX 5.0 SP2group counter

NoAllocs (tag 78) is a NumInGroup field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 13 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
78
Name
NoAllocs
Datatype
NumInGroup (int)
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
13

What the specification says

FIX 4.4

Number of repeating AllocAccount (79)/AllocPrice (366) entries.

FIX 4.2

Number of repeating AllocAccount/AllocPrice entries.

FIX 5.0 SP2

Number of repeating AllocAccount (79)/AllocPrice (366) entries.

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

A real message using tag 78

NewOrderSingle · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength138
35MsgTypeDOrder – Single
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
11ClOrdIDORD-10042
78NoAllocs2 entries2repeating group
79AllocAccountEXAMPLE
79AllocAccountEXAMPLE
54Side1Buy
60TransactTime20240101-12:00:00.000
40OrdType1Market
10CheckSum076
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 78 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.2FIX 5.0 SP2Where in the message
AllocationInstructionJOptionalOptionalOptionalinside the AllocGrp component
AllocationInstructionAckPOptionalOptionalinside the AllocAckGrp component
AllocationInstructionAlertBMOptionalinside the AllocGrp component
AllocationReportASOptionalOptionalinside the AllocGrp component
AllocationReportAckATOptionalOptionalinside the AllocAckGrp component
CrossOrderCancelReplaceRequesttOptionalOptionalinside SideCrossOrdModGrp › PreAllocGrp
ExecutionReport8Optionalinside the PreAllocGrp component
MultilegOrderCancelReplaceACOptionalOptionalinside the PreAllocMlegGrp component
NewOrderCrosssOptionalOptionalinside SideCrossOrdModGrp › PreAllocGrp
NewOrderListEOptionalOptionalOptionalinside ListOrdGrp › PreAllocGrp
NewOrderMultilegABOptionalOptionalinside the PreAllocMlegGrp component
NewOrderSingleDOptionalOptionalOptionalinside the PreAllocGrp component
OrderCancelReplaceRequestGOptionalOptionalOptionalinside the PreAllocGrp component
TradeCaptureReportAEOptionalOptionalinside TrdCapRptSideGrp › TrdAllocGrp
TradeCaptureReportAckAROptionalOptionalinside the TrdAllocGrp 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 78 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);// NoAllocs is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[78] is undefined.const entries = message.groups[78] ?? [];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