{{Quickfixn}} String to Boolean error

[Grant Birchmeier]

According to FIXimate, booleans are indeed only "Y" or "N".  Your
counterparty has made a mistake (though an understandable one).

Changing it to a string in your definition file is a good workaround.

I don't know if the other QFs accept values other than Y/N.

It would not be difficult to adapt QF/n to accept 0/1.  I don't know if
that's a good idea, but I don't think it's a bad idea.


On Thu, Feb 6, 2014 at 12:09 PM, Manuel Lopez <lopez.post at gmail.com> wrote:

> I'm getting a puzzling error in my logs:
> 20140206-16:43:09.435 : Could not convert field: Cannot convert string to
> boolean
> 20140206-16:43:09.435 : Message 824 Rejected: Incorrect data format for
> value (Field=6082)
>
> The puzzle is that field 6082 in my message log is a Boolean value
> (6082=1).  It seems that strictly speaking FIX defines only 'Y' or 'N' as
> Boolean?
>
> If this is correct, I'll speak to my counterparty; but is there an
> argument for a looser definition of Boolean as 1 or 0 and not just Y or N?
>
> I'll define that field as string in my definition file.
>
> I'm not sure that quickfix has ever rejected 0 for Boolean.
>
>
>
> _______________________________________________
> Quickfixn mailing list
> Quickfixn at lists.quickfixn.com
> http://lists.quickfixn.com/listinfo.cgi/quickfixn-quickfixn.com
>
>


-- 
Grant Birchmeier
*Connamara Systems, LLC*
*Made-To-Measure Trading Solutions.*
Exactly what you need. No more. No less.
http://connamara.com
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.quickfixn.com/pipermail/quickfixn-quickfixn.com/attachments/20140206/3565995a/attachment-0002.htm>