MultilegPriceMethod (FIX tag 1378)
MultilegPriceMethod (tag 1378) is an int field defined in FIX 5.0 SP2. It appears in 10 message types, always optionally. It is an enumerated field with 6 defined values.
At a glance
- Tag
- 1378
- Name
- MultilegPriceMethod
- Datatype
- int
- Dialects
- FIX 5.0 SP2
- Messages
- 10
- Valid values
- 6
What the specification says
Code to represent how the multileg price is to be interpreted when applied to the legs.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1378
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 137 | |
| 35 | MsgType | AB | NewOrderMultileg |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 11 | ClOrdID | ORD-10042 | |
| 54 | Side | 1 | Buy |
| 555 | NoLegs1 entry | 1 | repeating group |
| 600 | LegSymbol | EXAMPLE | |
| 60 | TransactTime | 20240101-12:00:00.000 | |
| 40 | OrdType | 1 | Market |
| 1378 | MultilegPriceMethod | 0 | Net Price |
| 10 | CheckSum | 180 |
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.
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 |
|---|---|---|
| 0 | Net Price | NET_PRICE |
| 1 | Reversed Net Price | REVERSED_NET_PRICE |
| 2 | Yield Difference | YIELD_DIFFERENCE |
| 3 | Individual | INDIVIDUAL |
| 4 | Contract Weighted Average Price | CONTRACT_WEIGHTED_AVERAGE_PRICE |
| 5 | Multiplied Price | MULTIPLIED_PRICE |
Where tag 1378 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 |
|---|---|---|---|
| DerivativeSecurityList | AA | Optional | inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules |
| DerivativeSecurityListUpdateReport | BR | Optional | inside DerivativeSecurityDefinition › MarketSegmentGrp › SecurityTradingRules › BaseTradingRules |
| MarketDefinition | BU | Optional | inside the BaseTradingRules component |
| MarketDefinitionUpdateReport | BV | Optional | inside the BaseTradingRules component |
| MultilegOrderCancelReplace | AC | Optional | directly on the message body |
| NewOrderMultileg | AB | Optional | directly on the message body |
| SecurityDefinition | d | Optional | inside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules |
| SecurityDefinitionUpdateReport | BP | Optional | inside MarketSegmentGrp › SecurityTradingRules › BaseTradingRules |
| SecurityList | y | Optional | inside SecListGrp › SecurityTradingRules › BaseTradingRules |
| SecurityListUpdateReport | BK | Optional | inside SecLstUpdRelSymGrp › SecurityTradingRules › BaseTradingRules |
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 1378 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);const multilegPriceMethod = message.fields[1378]?.raw;// e.g. "0" — Net Price// The dictionary also carries the labels:const label = fix.dictionary .fieldByTag(1378) ?.enumValues?.find((e) => e.value === multilegPriceMethod) ?.description;Other int fields
- 1377MultilegModel
- 1376MassActionRejectReason
- 1375MassActionResponse
- 1374MassActionScope
- 1373MassActionType
- 1385ContingencyType
- 1386ListRejectReason
- 1368TradSesEvent
- 1388TrdRepPartyRole
- 1390TradePublishIndicator
- 1361TotNoFills
- 1358LegPutOrCall
- 1400EncryptedPasswordMethod
- 1354ApplResponseError
- 1406RefApplExtID
- 1349ApplTotalMessageCount
- 1407DefaultApplExtID
- 1348ApplResponseType
- 1347ApplReqType
- 1409SessionStatus
- 1411Nested4PartySubIDType
- 1343UnderlyingLegPutOrCall
- 1417Nested4PartyRole
- 1419UnderlyingExerciseStyle
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