NoCapacities (FIX tag 862)

NumInGroupFIX 4.4group counter

NoCapacities (tag 862) is a NumInGroup field defined in FIX 4.4. It appears in 1 message type and is required in 1 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
862
Name
NoCapacities
Datatype
NumInGroup (int)
Dialects
FIX 4.4
Messages
1

What the specification says

Number of repeating OrderCapacity entries.

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

A real message using tag 862

Confirmation · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength238
35MsgTypeAKConfirmation
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
664ConfirmIDEXAMPLE
666ConfirmTransType0New
773ConfirmType1Status
665ConfirmStatus1Received
60TransactTime20240101-12:00:00.000
75TradeDate20240101
80AllocQty1000000
54Side1Buy
862NoCapacities2 entries2repeating group
528OrderCapacityAAgency
863OrderCapacityQty1000000
528OrderCapacityAAgency
863OrderCapacityQty1000000
79AllocAccountEXAMPLE
6AvgPx1.09215
381GrossTradeAmt125000.00
118NetMoney125000.00
10CheckSum099
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 862 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.

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