StandInstDbID (FIX tag 171)

StringFIX 4.4FIX 4.2

StandInstDbID (tag 171) is a String field defined in FIX 4.4 and FIX 4.2. It appears in 8 message types, always optionally.

At a glance

Tag: 171
Name: StandInstDbID
Datatype: String
Dialects: FIX 4.4 and FIX 4.2
Messages: 8

What the specification says

Unique identifier used on the Standing Instructions database for the Standing Instructions to be referenced.

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

A real message using tag 171

AllocationInstruction · FIX 4.4

Tag	Field	Wire value	Meaning
8	BeginString	FIX.4.4
9	BodyLength	180
35	MsgType	J	Allocation Instruction
49	SenderCompID	BOARTEAM
56	TargetCompID	COUNTERPARTY
34	MsgSeqNum	2
52	SendingTime	20240101-12:00:00.000
70	AllocID	EXAMPLE
71	AllocTransType	0	New
626	AllocType	1	Calculated (includes MiscFees and NetMoney)
857	AllocNoOrdersType	0	Not specified
54	Side	1	Buy
53	Quantity	1000000
6	AvgPx	1.09215
75	TradeDate	20240101
78	NoAllocs2 entries	2	repeating group
79	AllocAccount	EXAMPLE
171	StandInstDbID	EXAMPLE
79	AllocAccount	EXAMPLE
171	StandInstDbID	EXAMPLE
10	CheckSum	142

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 171 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	FIX 4.4	FIX 4.2	Where in the message
AllocationInstruction	J	Conditional	—	inside AllocGrp › SettlInstructionsData
AllocationReport	AS	Conditional	—	inside AllocGrp › SettlInstructionsData
CollateralAssignment	AY	Conditional	—	inside the SettlInstructionsData component
CollateralInquiry	BB	Conditional	—	inside the SettlInstructionsData component
CollateralReport	BA	Conditional	—	inside the SettlInstructionsData component
Confirmation	AK	Conditional	—	inside the SettlInstructionsData component
SettlementInstructionRequest	AV	Conditional	—	directly on the message body
SettlementInstructions	T	Conditional	Optional	inside SettlInstGrp › SettlInstructionsData

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

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

Try the decoder Source on GitHub