NoAsgnReqs (FIX tag 1499)
NoAsgnReqs (tag 1499) is a NumInGroup field defined in FIX 5.0 SP2. It appears in 2 message types, always optionally. Its datatype is NumInGroup, which makes it a repeating-group counter: its value is the number of entries that follow, not a quantity in its own right.
At a glance
- Tag
- 1499
- Name
- NoAsgnReqs
- Datatype
- NumInGroup (int)
- Dialects
- FIX 5.0 SP2
- Messages
- 2
What the specification says
Number of assignment requests.
Descriptions are quoted from the FIX Orchestra sources under the Apache 2.0 licence.
A real message using tag 1499
| Tag | Field | Wire value | Meaning |
|---|---|---|---|
| 8 | BeginString | FIXT.1.1 | |
| 9 | BodyLength | 127 | |
| 35 | MsgType | CC | StreamAssignmentRequest |
| 49 | SenderCompID | BOARTEAM | |
| 56 | TargetCompID | COUNTERPARTY | |
| 34 | MsgSeqNum | 2 | |
| 52 | SendingTime | 20240101-12:00:00.000 | |
| 1497 | StreamAsgnReqID | EXAMPLE | |
| 1498 | StreamAsgnReqType | 1 | Stream assignment for new customer(s) |
| 1499 | NoAsgnReqs2 entries | 2 | repeating group |
| 453 | NoPartyIDs1 entry | 1 | repeating group |
| 448 | PartyID | EXAMPLE | |
| 453 | NoPartyIDs1 entry | 1 | repeating group |
| 448 | PartyID | EXAMPLE | |
| 10 | CheckSum | 024 |
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.
Where tag 1499 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 |
|---|---|---|---|
| StreamAssignmentReport | CD | Optional | inside the StrmAsgnRptGrp component |
| StreamAssignmentRequest | CC | Optional | inside the StrmAsgnReqGrp component |
Wire format
The number of entries in the repeating group that follows. The next field on the wire is the group's delimiter tag. @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 1499 in TypeScript
import { createFixEngine } from "@boarteam/fix";import { dictionary } from "@boarteam/fix-dict-fix50sp2";const fix = createFixEngine(dictionary);const { message, issues } = fix.parse(raw);// NoAsgnReqs is a group counter, so the entries live on message.groups —// NOT on message.fields. message.fields[1499] is undefined.const entries = message.groups[1499] ?? [];for (const entry of entries) { // entry.fields is keyed by tag; entry.groups holds nested groups}Other NumInGroup fields
- 1494NoComplexEventTimes
- 1491NoComplexEventDates
- 1483NoComplexEvents
- 1475NoNewsRefIDs
- 1461NoTargetPartyIDs
- 1445NoRateSources
- 1414NoNested4PartyIDs
- 1413NoNested4PartySubIDs
- 1387NoTrdRepIndicators
- 1370NoNotAffectedOrders
- 1362NoFills
- 1351NoApplIDs
- 1342NoOfLegUnderlyings
- 1334NoUnderlyingLegSecurityAltID
- 1312NoNestedInstrAttrib
- 1311NoDerivativeInstrAttrib
- 1310NoMarketSegments
- 1309NoTradingSessionRules
- 1296NoDerivativeInstrumentPartySubIDs
- 1292NoDerivativeInstrumentParties
- 1286NoDerivativeEvents
- 1239NoTimeInForceRules
- 1237NoOrdTypeRules
- 1236NoMaturityRules
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