Tag number, field name, MsgType, message or component name, or a value such as 39=1 or OrdStatus=2. Search runs in your browser.
MDEntryID <278>
- Tag
278- Type
- String
- FIXML name
MDID- Category
- MarketData
- Pedigree
- Added FIX 4.2 · Updated FIX 5.0SP2 EP125
- Versions
- FIX Latest ✓ · FIX 4.4 ✓ · FIX 4.2 ✓
MDEntryID <278> in plain English
Summary by The MidPoint News, based on the description in the Orchestra file (quoted in full below).
MDEntryID is a unique identifier for a market data entry. Later updates can refer back to it.
Where it is used
ExecutionReport (35=8), MDFullGrp (repeating group), MDIncGrp (repeating group), MDAckGrp (repeating group) .
In all, 4 messages in FIX Latest can carry it. Full list.
Example message
8=FIXT.1.1|9=123|35=X|49=BUYSIDE|56=SELLSIDE|34=215|52=20261116-08:30:00.000|262=MDR-1|268=1|279=0|269=0|55=AAPL|270=190.46|271=200|278=E-1|10=057 Illustrative example, not real orders or market data. A MarketDataIncrementalRefresh (35=X) in FIX Latest, shown with BeginString FIXT.1.1. 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 Latest dictionary, but it is not a complete specification of the message.
Description (from the Orchestra file)
Unique Market Data Entry identifier.
Used in
Messages (1)
| Message | MsgType | Presence |
|---|---|---|
| ExecutionReport | 8 | Optional |
Components and repeating groups (3)
| Name | Kind | Presence |
|---|---|---|
| MDFullGrp | Repeating group | Optional |
| MDIncGrp | Repeating group | Optional |
| MDAckGrp | Repeating group | Optional |