ProgRptReqs (FIX tag 414)

intFIX 4.4FIX 4.2

ProgRptReqs (tag 414) is an int field defined in FIX 4.4 and FIX 4.2. It appears in 2 message types, always optionally. It is an enumerated field with 3 defined values.

At a glance

Tag: 414
Name: ProgRptReqs
Datatype: int
Dialects: FIX 4.4 and FIX 4.2
Messages: 2
Valid values: 3

What the specification says

FIX 4.4

Code to identify the desired frequency of progress reports

FIX 4.2

Code to identify the desired frequency of progress reports.

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

A real message using tag 414

NewOrderList · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	119
35	MsgType	E	Order – List
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
66	ListID	EXAMPLE
414	ProgRptReqs	1	BuySide explicitly requests status using StatusRequest (Default) The sell-side firm can however, send a DONE status List Status Response in an unsolicited fashion
394	BidType	1	"Non Disclosed" Style (e.g. US/European)
68	TotNoOrders	1
73	NoOrders1 entry	1	repeating group
11	ClOrdID	ORD-10042
67	ListSeqNo	1
54	Side	1	Buy
10	CheckSum	213

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.

Valid values

A value outside this list is not a parse error — the message still decodes — but validate() reports it as validate/value-not-in-enum.

Value	Meaning	Symbolic name
1	BuySide explicitly requests status using StatusRequest (Default) The sell-side firm can however, send a DONE status List Status Response in an unsolicited fashion	BUYSIDE_EXPLICITLY_REQUESTS_STATUS_USING_STATUSREQUEST / BuySideRequests
2	SellSide periodically sends status using ListStatus. Period optionally specified in ProgressPeriod	SELLSIDE_PERIODICALLY_SENDS_STATUS_USING_LISTSTATUS_PERIOD_OPTIONALLY_SPECIFIED_IN_PROGRESSPERIOD / SellSideSends
3	Real-time execution reports (to be discouraged)	REAL_TIME_EXECUTION_REPORTS / RealTimeExecutionReports

Where tag 414 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
BidRequest	k	Optional	Optional	directly on the message body
NewOrderList	E	Optional	Optional	directly on the message body

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 414 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 progRptReqs = message.fields[414]?.raw;// e.g. "1" — BuySide explicitly requests status using StatusRequest (Default) The sell-side firm can however, send a DONE status List Status Response in an unsolicited fashion// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(414)  ?.enumValues?.find((e) => e.value === progRptReqs)  ?.description;

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