TotNoQuoteEntries (FIX tag 304)

intFIX 4.4FIX 4.2

TotNoQuoteEntries (tag 304) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types and is required in 1 of them. FIX 4.2 calls this field TotQuoteEntries; the tag number is unchanged, so the two are the same field on the wire.

Also known as TotQuoteEntries

FIX 4.2 calls tag 304 TotQuoteEntries. It is the same field on the wire — only the name changed — so a message encoded by either side interoperates.

At a glance

Tag: 304
Name: TotNoQuoteEntries
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 2

What the specification says

FIX 4.4

Total number of quotes for the quote set across all messages. Should be the sum of all NoQuoteEntries (295) in each message that has repeating quotes that are part of the same quote set. (Prior to FIX 4.4 this field was named TotQuoteEntries)

FIX 4.2

Total number of quotes for the quote set across all messages. Should be the sum of all NoQuoteEntries in each message that has repeating quotes that are part of the same quote set.

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

A real message using tag 304

MassQuoteAcknowledgement · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	111
35	MsgType	b	Mass Quote Acknowledgement
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
297	QuoteStatus	0	Accepted
296	NoQuoteSets2 entries	2	repeating group
302	QuoteSetID	EXAMPLE
304	TotNoQuoteEntries	1
302	QuoteSetID	EXAMPLE
304	TotNoQuoteEntries	1
10	CheckSum	245

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 304 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
MassQuote	i	Required	Required	inside the QuotSetGrp component
MassQuoteAcknowledgement	b	Conditional	Optional	inside the QuotSetAckGrp component

Wire format

A whole number, optionally signed. Leading zeros are legal on the wire and are preserved in the raw value. @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 304 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);const field = message.fields[304];field?.name;   // "TotNoQuoteEntries"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a number

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