Friday, 20 November 2026 · Free. No paywall. No subscription.
Search The MidPoint News

Search articles, videos and sections. Press / to open, Esc to close.

FIX 4.2Field

MDEntryRefID <280>

Tag
280
Type
String
Pedigree
Added FIX 4.2
Versions
FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓

This page shows MDEntryRefID <280> as defined in FIX 4.2. For the current standard, see tag 280 MDEntryRefID in FIX Latest.

MDEntryRefID <280> in plain English

Summary by The MidPoint News, based on the FIX Latest description in the Orchestra file. The FIX 4.2 description is quoted in full below and may differ.

MDEntryRefID refers to an earlier MDEntryID (278).

Where it is used

MDIncGrp (repeating group) . In all, 1 message in FIX 4.2 can carry it. Full list.

Example message

8=FIX.4.2|9=131|35=X|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|262=MDR-1|268=1|279=1|269=0|55=AAPL|270=190.46|271=200|278=E-2|280=E-1|10=101

Illustrative example, not real orders or market data. A MarketDataIncrementalRefresh (35=X) in FIX 4.2, shown with BeginString FIX.4.2. Instrument identifiers (such as AAPL, ISIN US0378331005, ESZ6, XNAS, XCME) are real public codes used for illustration. Order and execution IDs, accounts, prices, quantities and times are made up. Fields are separated by | here; on the wire the separator is the SOH character (ASCII 1). BodyLength (9) and CheckSum (10) are calculated for this example. Every tag and value in it is checked against the FIX 4.2 dictionary, but it is not a complete specification of the message.

Related tags: MDEntryID <278>

Description (from the Orchestra file)

Refers to a previous MDEntryID.

Used in

Components and repeating groups (1)

NameKindPresence
MDIncGrpRepeating groupOptional
All 1 messages that can carry MDEntryRefID, including through components and groups