Feature Requests

, ,
1

Imported from previous forum

2

Please suggest any features you would like to see.

5

Could you please allow searching of fields within FIXimate by the FixML names. I don’t know about anyone else, but I am familiar with the FixML names rather than the Field Names. It’s very frustrating to search for a field by name (e.g. “PxTyp”) only to be told that that field is unknown in FIX (in this example it will only show results for “PriceType”), and to then have to expand all the nodes in the message and do a text search on the page.

6

This relates to the internals of FIXimate rather than the website itself- will pass the request to the appropriate parties.

7

Many thanks. :slight_smile:

8

Thanks for the request which we will look into. A few comments on the options you currently have. A lot of the FIXML abbreviations are identical across a large number of distinct FIX fields, e.g. @ID, @Src. A few FIX fields also have two FIXML abbreviations, depending on the context, e.g. ClOrdID(11) has @ID in SingleGeneralOrderHandling and @ClOrdID anywhere else. The abbreviations are largely standardised, e.g. “Px” typically (but not always) stands for “Price”.

FIXimate allows you to just enter parts of a FIX field name, e.g. if you know it has “Price” in it then you can try to only search for that term and do not have to enter the complete field name.

You can expand all nodes (components) in a message with a single click on a small text right above the message table that says “Expand Components | Collapse Components”.

A workaround is also to display all fields in FIXimate and then use the search capability of your browser to find a specific FIXML abbreviation. That is only needed if you do not know which message the field may be part of.

9

I guess when I’m searching for a specific tag by name, it’s normally either so I can see the valid values for that tag, or to see which messages/components it’s valid in, so really I’m just looking for the quickest way to get ahold of the details for that tag.

Ideally, you would allow searching on all the possible names for each tag (so allow both ClOrdID and ID) and bring up a list of all possible matches if multiple (as you currently do with your RegEx search), or the tag details if unique. To be fair, I don’t think many people would search for ID, and if they did, they wouldn’t expect it to be unique.

But your other tips are useful, so I’ll bear them in mind.

Thanks.