NoIOIQualifiers (FIX tag 199)

NumInGroupFIX 4.4FIX 4.2group counter

NoIOIQualifiers (tag 199) is a NumInGroup field defined in FIX 4.4 and FIX 4.2. It appears in 1 message type, 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: 199
Name: NoIOIQualifiers
Datatype: NumInGroup (int)
Dialects: FIX 4.4 and FIX 4.2
Messages: 1

What the specification says

FIX 4.4

Number of repeating groups of IOIQualifiers (04).

FIX 4.2

Number of repeating groups of IOIQualifiers.

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

A real message using tag 199

IOI · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	107
35	MsgType	6	Indication of Interest
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
23	IOIID	EXAMPLE
28	IOITransType	N	New
54	Side	1	Buy
27	IOIQty	S	Small
199	NoIOIQualifiers2 entries	2	repeating group
104	IOIQualifier	A	All or none
104	IOIQualifier	A	All or none
10	CheckSum	149

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 199 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	FIX 4.4	FIX 4.2	Where in the message
IOI	6	Optional	Optional	inside the IOIQualGrp 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 199 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);// NoIOIQualifiers is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[199] is undefined.const entries = message.groups[199] ?? [];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