Two things you should be aware of
- You should not be using MRM XML in a new message flow. XMLNSC is the recommended parser for almost all XML processing.
- The MRM parser does not use field types ( XML.Attr ) to identify attributes. It matches the structure of the message tree against the message definition. If you insist on using MRM XML, you will have to change your message definition and make isChanged an attribute.
In that case, the structure of your message tree does not match your message definition. It's a common problem, and it proves that MRM XML is not being used correctly. You might as well use XMLNSC.
You cannot post new topics in this forum You cannot reply to topics in this forum You cannot edit your posts in this forum You cannot delete your posts in this forum You cannot vote in polls in this forum