[This message was posted by John Prewett of Lava Trading <[EMAIL PROTECTED]> to the "General Q/A" discussion forum at http://fixprotocol.org/discuss/22. You can reply to it on-line at http://fixprotocol.org/discuss/read/9c112af8 - PLEASE DO NOT REPLY BY MAIL.]
Greg, I respectfully suggest that you may have misread the original question. The original posting indicates that the receiver is obligating that the Stipulations repeating group (in its entirety) must appear in the message after the Account tag. I still believe this doesn't match with standard FIX protocol. The original posting has nothing to do with the order of fields within a repeating group or the repeat count that must occur prior to the repeating group. Incidentally, the sender does indeed correctly honor the repeat count field followed by the repeating block fields in the correct order according to his original posting. JohnP > I agree with the counter-party - order is enforced in this case. > > The question relates to repeating groups. Note the fields in question: > > > > des(552)=1|Side(54)=1|NoStipulations(232)=1|StipulationType(233)=TE- > > > ST|StipulationValue(234)=N > > NoSides(552) is a NumInGroup type that defines the number of > 'TrdCapRptSideGrp' elements to follow. The order of the tags in this > element is fixed and must follow the order in the specification. > > Greg. > > > > TransactTools support is correct (although field order is also > > important for BeginString, MsgLength, MsgType & CheckSum too). The > > other company isn't obeying FIX protocol standards that basically > > permits fields to occur in any order. > > > > JohnP > > > > > We are sending FIX messages to another company who has very strict > > > FIX parsing for the order of the fields. > > > > > > For example, in TradeCaptureReport message, we are sending a > > > stipulation block. > > > > > > des(552)=1|Side(54)=1|NoStipulations(232)=1|StipulationType(233)=TE- > > > ST|StipulationValue(234)=N > > > > > > The other side is rejecting our message, and is saying stipulations > > > "need to be sent later in the message - after the account (tag 1)". > > > > > > In addition, they also complain that we send OrderID tag out of > > > place. They claim we need to send tag NoSides(552), then Side(54), > > > then 37 (OrderID). We are sending tag 37 after PartyRole(452). > > > > > > Unfortunately we don't have control over this. We are using > > > TransactTools which orders these automatically. We have tried > > > contacting their support and they say order does not matter in FIX > > > except for in repeating groups and there is nothing we can do. > > > > > > So what is the official word on ordering here? [You can unsubscribe from this discussion group by sending a message to mailto:[EMAIL PROTECTED] --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Financial Information eXchange" group. To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/FIX-Protocol?hl=en -~----------~----~----~----~------~----~------~--~---
