Posted: Fri Nov 06, 2009 11:46 am Post subject: CSV Message set
Centurion
Joined: 10 Oct 2002 Posts: 136 Location: California
Hi,
I have created a CSV message set using TDS. It has All element Delmited with delimiter as comma. The message set parses regular message properly without any issue.
However if the message is short - Message set definition has 110 fields but message only has 10 fields, it does not throw me an error even though I have marked all fields as required. The Same is the case if the message is long meaning message has more than 110 fields. It just puts all the values after 109th field into 110th field.
I also tried deploying the Sample CSV Message set and flow that is supplied in samples gallery. It also gives me same behaviour. I am using WMB 6.0. Is that a feature or a Bug? I expected the message to fail and give parser error if the message was short or long.
The MRM parser does not complain about missing fields if it can continue parsing. If you want strict validation of your message, set Validation to 'Content and Value' on the input node.
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