Search by field name does not work for fields with alternative names

, ,
1

Imported from previous forum

2

In FIX 4.2 tag 47 has official name “Rule80A” and alternative (legacy) name “OrderCapacity”. But if you would enter either “Rule80A” or “OrderCapacity” string in “Field by name:” field and client “Go”, you would get “tag is unknown” error. If you would enter “Rule80A(aka OrderCapacity)” string into “Field by name:” search would succeed. This is weird.

3

Priviet Mikael,

I think because the name has alrteady been changed to OrderCapacity instead. Because they have mapped it that way in the search engine. It will recognise only "Rule80A (aka Ordercapacity). There are still many user who refer to it as “Rule80A” thought.

Joel

Note that the name of this field is changing to “OrderCapacity” as Rule80A is a very US market-specific term. Other world markets need to convey similar information, however, often a subset of the US values. . See the “Rule80A (aka OrderCapacity) Usage by Market” appendix for market-specific usage of this field.

In FIX 4.2 tag 47 has official name “Rule80A” and alternative (legacy)
name “OrderCapacity”. But if you would enter either “Rule80A” or
“OrderCapacity” string in “Field by name:” field and client “Go”, you
would get “tag is unknown” error. If you would enter “Rule80A(aka
OrderCapacity)” string into “Field by name:” search would succeed.
This is weird.