Imported from previous forum
Anybody know how to handle optional fields for which we have no value if it appears in a repeating block ?
To illustrate : take a hypothetical repeated block
where <20>=<number of repeats> and <21>,<22>,<23> are all optional fields that make up the repeat.
If I only have 2 as the number of repeats and 2 values for the <21> tag only, how do I generate this block of repeats?
Do I leave out tags <22> and <23> ?
eg. 20=2<SOH>21=value1<SOH>21=value2<SOH>
Or do I produce dummy / empty values for tags <22> and <23> ?
eg. 20=2<SOH>21=value1<SOH>22=<SOH>23=<SOH> 21=value2<SOH>22=<SOH>23=<SOH> ?
Any comments or suggestions would be welcome
My previous post did not fully explain my problem.
What I was asking was : if one receives a repeating sequence that has optional fields (hence missing in the sequence) how does one know which of the supplied fields belongs to which loop
in the sequence. In the example I supplied , the first field was always present making interpretation obvious.
> Anybody know how to handle optional fields for which we have no value if it appears in a repeating block ?
>
> To illustrate : take a hypothetical repeated block
> where <20>=<number of repeats> and <21>,<22>,<23> are all optional fields that make up the repeat.
> If I only have 2 as the number of repeats and 2 values for the <21> tag only, how do I generate this block of repeats?
>
> Do I leave out tags <22> and <23> ?
> eg. 20=2<SOH>21=value1<SOH>21=value2<SOH>
>
> Or do I produce dummy / empty values for tags <22> and <23> ?
> eg. 20=2<SOH>21=value1<SOH>22=<SOH>23=<SOH> 21=value2<SOH>22=<SOH>23=<SOH> ?
>
> Any comments or suggestions would be welcome
>
>
>
>
>
> My previous post did not fully explain my problem.
> What I was asking was : if one receives a repeating sequence that has optional fields (hence missing in the sequence) how does one know which of the supplied fields belongs to which loop
> in the sequence. In the example I supplied , the first field was always present making interpretation obvious.
You have a point. This is something that should be formalized and explained in further revisions of the spec.
In 4.1, all rep groups have a required field as the first repeating field in the group. This is true with one exception, which has the second repeating field as required.
If this stays true, it is possible to parse rep groups with different number of fields in each repetition.
Ulf Eriksson - Interbizz Financial Systems
Ulf, you are correct. The one exception (Execs repeating group within the Allocation message) was an oversight. FIX 4.1 intended to make the first field in every repeating group required if that group was being used. The sole exception has been addressed by the "Errata" for FIX 4.1 which was recently made available within the "Specifications" section. In the future we will ensure that if a repeating group is to be used, the first field within the repeating group is required.
> > My previous post did not fully explain my problem.
> > What I was asking was : if one receives a repeating sequence that has optional fields (hence missing in the sequence) how does one know which of the supplied fields belongs to which loop
> > in the sequence. In the example I supplied , the first field was always present making interpretation obvious.
>
>
> You have a point. This is something that should be formalized and explained in further revisions of the spec.
>
> In 4.1, all rep groups have a required field as the first repeating field in the group. This is true with one exception, which has the second repeating field as required.
>
> If this stays true, it is possible to parse rep groups with different number of fields in each repetition.
>
> Ulf Eriksson - Interbizz Financial Systems
>
>
>