Originally posted by: repanzer1
Laurent, did you use to post under a different screen name?
JasonJava,
Ok, if I'm reading you correctly...you have a group which can contain two different record types. The first record type can occur any amount of times (0:s) and each has a three character numeric initiator from 010 through 099. The second record type does not have a three character numeric initiator.
In the example data you posted, when the map ran, it read 010, 011, and 014 fine, but got an error on the next record that starts with TTT, because the map tried to validate it as the record above it, rather than know to skip to the next records definition.
The reason this happened is because you did not have an identifier set on the record.
You can do what Laurent suggested above and put that component rule on that field, ISNUMBER($) , but also, you have to set that field as the identifier. Open up the record's type and right click the first field and select "identifier".
Anytime you have this issue, where the map is validating and failing on an object instead of going to the next object, it's usually this problem.
Let us know how it goes.
There are 10 types of people in this world. Those who understand binary and those who don't.
#DataExchange#IBMSterlingTransformationExtender#IBM-Websphere-Transformation-Extender