FIX8 parser does the order of fields in xml spec matters?

[pT]

Hello suddenly seems like I am getting an error when trying to parse a fix8 execution report that a field is missing although the field is there.

0000096  in 8=FIX.4.29=38135=834=6849=Coinbase52=20230703-12:36:04.68256=decc5ad4434a494a2f861931ca692c62999=10284870666=4725.152956388939458314=0.0019774817=79a68ad8-e5c8-5ae8-b030-3f825a5c39d620=031=4907.7932=0.000465937=bd359e71-0aed-4fa9-9867-4704dc7e56ef39=144=4907.7954=155=BTC-USD60=20230703-12:36:04.678136=1137=0.006138=USD139=4150=1151=0.00802252891=21003=757854231057=Y10=067

0000064 out 8=FIX.4.29=13335=349=decc5ad4434a494a2f861931ca692c6256=Coinbase34=6452=20230703-12:36:04.67645=6858=Missing Mandatory Field: ExecType (150)10=025

The XML spec is the one here: 

https://docs.cloud.coinbase.com/exchange/docs/dictionaries#production-dictionary

Any idea whats the issue here?

[Ian McKane]

The parser can get confused. Usually means there is an invalid field somewhere in the message.

/Ian