Here is an example of a message that distributes market data. When the message is created the required field with the number of repeating groups is set to zero. This is because QuickFIX will automatically set this field for you when you add groups. This way there is never an inconsistancy between the number of entries in the field and in the message.
See this code in C#, VB.NET, PYTHON, RUBY// create a market data message FIX42::MarketDataSnapshotFullRefresh message(FIX::Symbol("QF")); // repeating group in the form of MessageName::NoField FIX42::MarketDataSnapshotFullRefresh::NoMDEntries group; group.set(FIX::MDEntryType('0')); group.set(FIX::MDEntryPx(12.32)); group.set(FIX::MDEntrySize(100)); group.set(FIX::OrderID("ORDERID")); message.addGroup(group); // no need to create a new group class if we are reusing the fields group.set(FIX::MDEntryType('1')); group.set(FIX::MDEntryPx(12.32)); group.set(FIX::MDEntrySize(100)); group.set(FIX::OrderID("ORDERID")); message.addGroup(group);
To pull a group out of a message you need to supply the group you wish to pull out. You should first inspect the number of entries field (which the group is named after) to get the total number of groups. The message that was created above is now parsed back out below.
See this code in C#, VB.NET, PYTHON, RUBY// should be 2 FIX::NoMDEntries noMDEntries; message.get(noMDEntries); FIX42::MarketDataSnapshotFullRefresh::NoMDEntries group; FIX::MDEntryType MDEntryType; FIX::MDEntryPx MDEntryPx; FIX::MDEntrySize MDEntrySize; FIX::OrderID orderID; message.getGroup(1, group); group.get(MDEntryType); group.get(MDEntryPx); group.get(MDEntrySize); group.get(orderID); message.getGroup(2, group); group.get(MDEntryType); group.get(MDEntryPx); group.get(MDEntrySize); group.get(orderID);