DeskID (FIX tag 284)

StringFIX 4.4FIX 4.2FIX 5.0 SP2

DeskID (tag 284) is a String field defined in FIX 4.4, FIX 4.2 and FIX 5.0 SP2. It appears in 4 message types, always optionally.

At a glance

Tag
284
Name
DeskID
Datatype
String
Dialects
FIX 4.4, FIX 4.2 and FIX 5.0 SP2
Messages
4

What the specification says

FIX 4.4

Identification of a Market Maker’s desk

FIX 4.2

Identification of a Market Maker’s desk

FIX 5.0 SP2

Identification of a Market Maker's desk

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

A real message using tag 284

MarketDataSnapshotFullRefresh · FIX 4.4
TagFieldWire valueMeaning
8BeginStringFIX.4.4
9BodyLength105
35MsgTypeWMarket Data-Snapshot/Full Refresh
49SenderCompIDBOARTEAM
56TargetCompIDCOUNTERPARTY
34MsgSeqNum2
52SendingTime20240101-12:00:00.000
268NoMDEntries2 entries2repeating group
269MDEntryType0Bid
284DeskIDEXAMPLE
269MDEntryType0Bid
284DeskIDEXAMPLE
10CheckSum000
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 284 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.

MessageMsgTypeFIX 4.4FIX 4.2FIX 5.0 SP2Where in the message
MarketDataIncrementalRefreshXOptionalOptionalOptionalinside the MDIncGrp component
MarketDataSnapshotFullRefreshWOptionalOptionalOptionalinside the MDFullGrp component
NetworkCounterpartySystemStatusRequestBCOptionalOptionalinside the CompIDReqGrp component
NetworkCounterpartySystemStatusResponseBDOptionalOptionalinside the CompIDStatGrp component

Wire format

Free-form text. Any byte except the SOH separator is legal, so values are not trimmed or case-folded on the wire. @boarteam/fix keeps the value as a string; format rules are checked by validate(), which reports validate/invalid-value rather than throwing.

Read tag 284 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[284];field?.name;   // "DeskID"field?.raw;    // the verbatim wire stringfield?.value;  // coerced to a string

Other String 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