DisplayMethod (FIX tag 1084)

charFIX 5.0 SP2

DisplayMethod (tag 1084) is a char field defined in FIX 5.0 SP2. It appears in 10 message types, always optionally. It is an enumerated field with 4 defined values.

At a glance

Tag: 1084
Name: DisplayMethod
Datatype: char
Dialects: FIX 5.0 SP2
Messages: 10
Valid values: 4

What the specification says

Defines what value to use in DisplayQty (1138). If not specified the default DisplayMethod is "1"

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

A real message using tag 1084

NewOrderSingle · FIX 5.0 SP2

Tag	Field	Wire value	Meaning
8	BeginString	FIXT.1.1
9	BodyLength	118
35	MsgType	D	NewOrderSingle
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
11	ClOrdID	ORD-10042
1084	DisplayMethod	1	Initial (use original DisplayQty)
54	Side	1	Buy
60	TransactTime	20240101-12:00:00.000
40	OrdType	1	Market
10	CheckSum	129

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 5.0 SP2 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	Initial (use original DisplayQty)	INITIAL
2	New (use RefreshQty)	NEW
3	Random (randomize value)	RANDOM
4	Undisclosed (invisible order)	UNDISCLOSED

Where tag 1084 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	Requiredness	Where in the message
CrossOrderCancelReplaceRequest	t	Optional	inside the DisplayInstruction component
ExecutionReport	8	Optional	inside the DisplayInstruction component
MultilegOrderCancelReplace	AC	Optional	inside the DisplayInstruction component
NewOrderCross	s	Optional	inside the DisplayInstruction component
NewOrderList	E	Optional	inside ListOrdGrp › DisplayInstruction
NewOrderMultileg	AB	Optional	inside the DisplayInstruction component
NewOrderSingle	D	Optional	inside the DisplayInstruction component
OrderCancelReplaceRequest	G	Optional	inside the DisplayInstruction component
TradeCaptureReport	AE	Optional	inside TrdCapRptSideGrp › TradeReportOrderDetail › DisplayInstruction
TradeCaptureReportAck	AR	Optional	inside TrdCapRptAckSideGrp › TradeReportOrderDetail › DisplayInstruction

Wire format

A single character. Most char fields are enumerated, so the value is one of a fixed set rather than arbitrary text. @boarteam/fix keeps the value as a string and, for enumerated fields, reports validate/value-not-in-enum when it is not a defined value.

Read tag 1084 in TypeScript

decode.tsts

import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const displayMethod = message.fields[1084]?.raw;// e.g. "1" — Initial (use original DisplayQty)// The dictionary also carries the labels:const label = fix.dictionary  .fieldByTag(1084)  ?.enumValues?.find((e) => e.value === displayMethod)  ?.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-fix50sp2

Try the decoder Source on GitHub