{{Quickfixn}} Error in Ruby 1.9.3 in generating custom XML field

[Manuel Lopez]

Ola,
Thanks.  No, it's actually "name" in the definition file, not
"description."  I think you're looking at the enums for the values
(which use "description"), not the field definitions (which use
"name").  There may (or may not) be a bug in the generator affected by
placement (don't know ruby so can't say); solved the problem by moving
the use of the new fields down in the message definitions.
Manuel

><field number="1028" name="ManualOrderIndicator" type="BOOLEAN" />

>'name' element should be 'description' check other fields and see how they are constructed.
>Best Regards
>Ola

On Mon, Dec 30, 2013 at 1:37 PM, Manuel Lopez <lopez.post at gmail.com> wrote:
> Ok I got it to work--there may or may not be a bug.  The ruby
> generation works after moving the line
>  <field name="ManualOrderIndicator" required="Y" />
> to the end of the message definitions in which it is included (in my
> case, NewOrderSingle and ExecutionReport).
>
> It was not embedded in a group or component or anything like that, but
> it still failed until I moved it to the end of the message definition.