When a field is defined of type "data", the orchesta xml type should define on the element an attribute lengthId, which value is equal to to id - 1 of the field as according to FIX protocol, the tag must always be preceded by its length:
Data fields are always immediately preceded by a length field
In the sample orchesta file for example, we can see field definition as:
<fixr:field name="RawData" added="FIX.2.7" type="data" abbrName="RawData" id="96" lengthId="95">
<fixr:annotation>
<fixr:documentation purpose="SYNOPSIS">
Unformatted raw data, can include bitmaps, word processor documents, etc.</fixr:documentation>
</fixr:annotation>
</fixr:field>
Where we see id="96" and lengthId="95". However, when generating the xml from, we obtain something like this:
<fixr:field type="data" id="96" name="RawData"/>
The lengthId attribute is dropped.
When a field is defined of type "data", the orchesta xml type should define on the element an attribute lengthId, which value is equal to to id - 1 of the field as according to FIX protocol, the tag must always be preceded by its length:
Data fields are always immediately preceded by a length field
In the sample orchesta file for example, we can see field definition as:
Where we see id="96" and lengthId="95". However, when generating the xml from, we obtain something like this:
<fixr:field type="data" id="96" name="RawData"/>The lengthId attribute is dropped.